On Wed, Apr 17, 2013 at 10:19:11AM +0200, Vincent Lefevre wrote: > On 2013-04-17 09:38:32 +0300, Niko Tyni wrote: > > On Wed, Apr 17, 2013 at 01:55:48AM +0200, Vincent Lefevre wrote:
> > > lib/perl5/<archname> doesn't exist yet initially, but I'd say > > > that's up to cpan to add it automatically when necessary. > > > > I wouldn't FWIW, but that's for upstream to decide. I certainly won't > > add a Debian deviation to do that. > > OK. Alternatively, it could be decided to add architecture-specific > directories whether they exist or not at interpreter startup time. Yes, that would fix it, at a cost of wasted stat() calls on module loading until the directory actually gets created. > > I note that newest versions of local::lib no longer suggest putting the > > arch-specific directory in PERL5LIB, precisely because Perl includes > > it automatically. I suspect this bootstrapping issue with nonexistent > > directories is not widely understood. > > Do you mean that architecture-specific directories are added even if > they don't exist at interpreter startup time? I just meant that the newest changes in local::lib probably make things worse wrt. this issue. -- Niko Tyni [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
