Eric Wilhelm wrote:
Most perl distributions set INSTALLDIRS=site in their CPAN config,
which is correct in this case.
So you're saying this is a debian bug and the problem lies with the
CPAN/CPANPLUS config? But then the user also needs to remember to set
this option when doing an install manually from the tarball.
The problem is in the Makefile.PL/Build.PL of a small handful of
distributions, right?
The summary seems to be:
1. installing in site is the right default
Only if #2 is true.
2. the perl default precedence core,site is wrong
2a. debian got that one right
Yes. @INC should be site, vendor, core.
Debian's Perl Policy is the best document on vendor supplied perls out there.
http://www.debian.org/doc/packaging-manuals/perl-policy/
3. dual-life modules have a habit of doing the wrong thing on debian
They should be setting INSTALLDIRS=site and --installdirs=site in their CPAN
shell configurations. That would solve the problem. I believe they do, at
least in the default configurations.
I'm saying that dual-life modules should install in site unless core has
higher precedence. Am I wrong?
Yes. Ideally site should have highest precedence and all locally installed
modules should go into site. That we hard code INSTALLDIRS=core on dual lifed
modules is because the default @INC is less than ideal.
--
Robrt: People can't win
Schwern: No, but they can riot after the game.
