[request-tracker-maintainers] RFC: rt-extension packaging

[KURASHIKI Satoru]

hi,

Thank you for your comments!

At Sat, 17 Dec 2011 12:12:14 +0000,
Dominic Hargreaves wrote:
> Okay. I haven't had a full look through your repo, but from a quick
> scan I note that you don't need to build rt3.8 packages any more (unless
> you have a particular need in the short term) as rt3.8 will be removed
> from wheezy at some point (#647126). (You definitely shouldn't build-dep
> on request-tracker3.8).

This is because I use rt3.8 for now.
Though I wish I could make this package backportable, I will drop
rt3.8 dependency.

> I assume you will do things like complete the long description(s) in
> debian/control, and update debian/copyright before release.

Sure :)

> However you only install a config snippet containing
> plugin-specific configuration variables - so don't try and override
> @Plugins! Tell the user to manually enable the plugin in their
> configuration.

> You'll need to call update-rt-siteconfig-n in your postinst after dropping
> config files in here.

OK, I will fix these issues.

> No, this is against Debian policy. This sounds like something which make
> JSGannt unsuitable for packaging at this stage - what is the change in
> the file? It is definitely not appropriate for a third party package to
> change the behaviour of RT outside of the scope of the extension
> mechanisms.

If it is packaged for only RT4 (>3.9), this patching is not needed (merged
into RT itself).
So, I will remove this for RT4, and tell the RT3.8 user to manually
patch this when backport.

regards,
-- 
KURASHIKI Satoru