[Pkg-trac-devel] Packaging of Trac plugins

[W. Martin Borgert]

Hi,

I filed some RFPs about some Trac plugins:

#504307: trac-email2trac -- email-to-ticket plugin for Trac
#504320: trac-customfieldadmin -- panel for administrating custom ticket fields in Trac
#504349: trac-announcer-plugin -- e-mail notification system for Trac
#504472: trac-diavisview-plugin -- renders dia files in Trac

Problem: The packages would be very small, so it's hard to
justify one package per plugin. OTOH, the plugins have
dependencies, that suggest to put them in their own package.
E.g. Why should someone who likes to use email2trac install dia?
So, for now, it's probably the best to package every plugin in
its own package.

Maybe we can later group the plugins:

- one package for ticket handling enhancements, such as
  email2trac and customfieldadmin (and later more trac-hacks)

- one package for misc. enhancements, such as announcer

- one package for completely new functions, such as
  testmanagement-plugin (with probably some dependencies)

- one package for content enhancements (with possibly a lot
  of dependencies to external programs and Python graphics libs)

However, I'm not sure, whether this will really keep the
dependencies low. E.g. for the masterticket-plugin, the use of
graphviz-plugin is necessary (or suggested?), which would again
lead to the situation, that someone who wants better ticket
handling ends up with dia and hundreds of Gnome libs. So this
solution needs more thinking.

Feel free to start packaging, otherwise I will have to do it :~)

Cheers!