Re: Bug#750017: perl-policy: All packages using Perl vendorarch directory need a perlapi-* dependency
On Sun, Jun 01, 2014 at 07:36:36PM +0200, Bill Allombert wrote:
> On Sun, Jun 01, 2014 at 07:09:13PM +0200, gregor herrmann wrote:
> > On Sun, 01 Jun 2014 09:53:11 -0700, Russ Allbery wrote:
> >
> > > Niko Tyni <ntyni@debian.org> writes:
> > > > I now realize that this wording unintentionally removes the perlapi
> > > > requirement for binary modules outside vendorarch (see for instance
> > > > the amanda-common package, which uses /usr/lib/amanda/perl/).
> > >
> > > > Revised patch attached. The new wording feels a bit awkward but
> > > > I guess it will do. Improvements and eyeballs welcome, of course.
> > >
> > > Ah, good catch. The new wording seems fine to me. Seconded.
> >
> > Improved wording seconded as well.
>
> This make three seconds, so let start a one week discussion period
> before I apply the patch.
Done. I added the following to upgrading-checklist:
<tag>perl</tag>
<item> Perl package should use the <tt>%Config</tt> hash to locate module
paths instead of hardcoding paths in <tt>@INC</tt>.
</item>
<tag>perl</tag>
<item> Perl binary modules and any modules installed into
<tt>$Config{vendorarch}</tt> must depend on the relevant
<package>perlapi-*</package> package.
Hoping this is adequate.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: