[request-tracker-maintainers] packaging of RT extensions

[Kai Storbeck]

On 8/28/13 12:09 AM, Dominic Hargreaves wrote:
> On Wed, Jun 19, 2013 at 03:06:02PM +0200, Kai Storbeck wrote:
>> Hello again,
>>
>> Thanks for the pointers last time. I've been happily hacking for a
>> while, and I'm bumping my head again.
>>
>> I'm proposing to craft a patch for RTx.pm to:
>> a) Listen to the INSTALLDIRS=vendor argument
>> b) Fix the DESTDIR bug (all 4 existing packages are hot patching the
>> issue or working around it).
>>
>> (There is an open pull-request for b [1], but its not merged yet)
>>
>> I would hope that we can suffice after this with an easy override
>> target, and without the need to override dh_auto_install:
>>
>>> override_dh_auto_configure:
>>>        RTHOME=/usr/share/request-tracker$(VERSION) dh_auto_configure
>>
>> Possibly with a loop to support multiple versions.
>>
>> I certainly like the sound of this, but before writing a patch I'd
>> like to have a general consensus about these things in general,
>> specifically for debians needs.
> 
> Hi Kai,
> 
> I'm sorry about the very long delay in replying to this; I've been
> pretty tied up in other projects for a while, but even so..
> 
> In the event that such feedback is useful, yes, this sounds like 
> idea, and I'd be happy to review code.

Hi Dom,

Thanks for your offer to help me.

I already wrote up some patches in June, but didn't publish it anywhere.
I've just pushed it to my github repo [1]. I made 2 branches:
 * honour-destdir-variable
 * support-vendorlib

As I stated earlier, the first (honour-destdir-variable) is already
filed upstream [2].

Its the second patch I'd definately like to get some input on:
support-vendorlib.

I came to my solution by looking at the contents of RT::Generated from
an installed version of request-tracker4. This currenlty includes a
variable already pointing to where the current packaged extensions
install their libs into:

>   $PluginPath = '/usr/share/request-tracker4/plugins';

I suppose LocalPluginPath is for manual installs of plugins? Then where
was PluginPath meant for?

Anyway, using this patch, the arguments given by dh_auto_configure will
now be used and stuff will be moved into the correct location.

What is missing is doing something useful with other valid values of
INSTALLDIRS [3]. Valid settings are perl, site and vendor. I could let
'site' install to RT::LocalPluginPath, which is more or less the current
behaviour if one doesn't supply an INSTALLDIRS argument.


Thanks,
Kai

[1] https://github.com/giganteous/module-install-rtx
[2] https://rt.cpan.org/Public/Bug/Display.html?id=12964
[3] http://perldoc.perl.org/ExtUtils/MakeMaker.html


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 906 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-request-tracker-maintainers/attachments/20130828/6b47e38c/attachment.sig>