I have a network of Gentoo boxen, and I build binary packages on one machine and install them on others.
Not all machine are in an identical state software-wise. Some are older than others, etc.
I've had the same issue on a number of occasions where I've installed Perl modules ( eg DBI, DBD-mysql, etc ) and had them installed into something like:
and then when I:
emerge -ukb --deep perl
to install binary packages from another PC, the @INC path is updated to ONLY the latest directory ( eg /usr/lib/perl5/5.8.5 ) which means that Perl can't see my modules in the older directories.
Steps to Reproduce:
1. Install Perl and Perl modules on system running a non-current Perl ( eg 5.8.4 )
2. Create binary packages with emerge -kb perl on a system running a current Perl ( eg 5.8.5 )
3. Install these binary packages on the first computer
The @INC path is set to the path on the system that built the packages.
The @INC path from the binary packages should be *merged* with the current @INC
Closing this bug as cantfix, but will sum up best I can:
What you're asking for isn't too possible. The paths included in @INC are determined in large part during compile time. If you then take that package and put it on another box, its going to get the @INC that was generated previously, not what you have on your new box.