Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 66480 - Emerging a pre-compiled package of Perl clobbers the @INC path
Summary: Emerging a pre-compiled package of Perl clobbers the @INC path
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-05 18:12 UTC by Daniel Kasak
Modified: 2004-12-21 06:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Kasak 2004-10-05 18:12:53 UTC
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:

/usr/lib/perl5/5.8.4

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.

Reproducible: Always
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

Actual Results:  
The @INC path is set to the path on the system that built the packages.

Expected Results:  
The @INC path from the binary packages should be *merged* with the current @INC
path.
Comment 1 Michael Cummings (RETIRED) gentoo-dev 2004-12-21 06:31:18 UTC
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.