After emerging Perl 5.8.8-r2 @inc is still: /etc/perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux /usr/lib64/perl5/vendor_perl/5.8.8 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux /usr/lib64/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /usr/lib64/perl5/5.8.8/x86_64-linux /usr/lib64/perl5/5.8.8 /usr/local/lib/site_perl If I interpreted the ebuild correctly, it should be site->vendor->core, after applying the reorder-INC.patch, which it does: >>> Unpacking source... >>> Unpacking perl-5.8.8.tar.bz2 to /var/tmp/portage/dev-lang/perl-5.8.8-r2/work ^[[32;01m*^[[0m Applying perl-prelink-lpthread.patch ... ^[[32;01m*^[[0m Applying perl-perldoc-emptydirs.patch ... ^[[32;01m*^[[0m Applying perl-5.8.8-reorder-INC.patch ... ^[[32;01m*^[[0m Applying perl-picdl.patch ... ^[[32;01m*^[[0m Applying perl-noksh.patch ... ^[[32;01m*^[[0m Applying perl-5.8.7-MakeMaker-RUNPATH.patch ... ^[[32;01m*^[[0m Applying perl-regexp-nossp.patch ... ^[[32;01m*^[[0m Applying perl-hppa-pa7200-configure.patch ... ^[[32;01m*^[[0m Applying perl-5.8.8-lib64.patch ... ^[[32;01m*^[[0m Applying perl-5.8.8-USE_MM_LD_RUN_PATH.patch ... ^[[32;01m*^[[0m Applying perl-5.8.8-links.patch ... ^[[32;01m*^[[0m Applying perl-5.8.8-cplusplus.patch ... Reproducible: Always Steps to Reproduce: 1. emerge perl 2. perl -V 3.
You are misunderstanding, actually. The desired order in gentoo is vendor->site->core, the idea being you can install via cpan (which defaults to site) and override core, but anything you install via portage trumps the lot.
(In reply to comment #1) > You are misunderstanding, actually. The desired order in gentoo is > vendor->site->core, the idea being you can install via cpan (which defaults to > site) and override core, but anything you install via portage trumps the lot. > Ok. But why does it say in the ebuild: # this lays the groundwork for solving the issue of what happens # when people (or ebuilds) install different versiosn of modules # that are in the core, by rearranging the @INC directory to look # site -> vendor -> core. cd ${S}; epatch ${FILESDIR}/${P}-reorder-INC.patch ... Mike
...which btw I think would be the better way: site->vendor->core, because it would let me decide wether I want to use cpan or not. cpan often has the newer packages. Ok, up to now I just rename vendor_perl, and just have i.e. razor residing in the original vendor path, but the normal update system/world would again break this arrangement. I like perl, because it lets you do things in different ways, and I think gentoo should be the same. Or at least it should give me a handy way to change @INC... Mike
