[request-tracker-maintainers] Packaging extensions

[Dominic Hargreaves]

Has anyone packaged RT extensions before? I'm probably going to want
to deploy at least one so I thought it would be best to package them
up properly. It probably makes sense for these to be maintained
within the team, in the svn repository.

I guess RTFM counts as one of these although that's a bit bigger than
most.

So I guess the only concrete question I have right now is package naming.

I'm thinking that we have a source package per distribution
(example: http://search.cpan.org/~nchuche/RTx-EmailCompletion-0.06/)

and binary packages for each supported major version of RT, with
files installed in /usr/share/request-tracker${VER}. So how about

rt-extension-emailcompletion (source)
rt-extension-emailcompletion-3.8 (binary)
rt-extension-emailcompletion-4.0 (... possible extra binary)

?

Any other ideas or observations?

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)