Re: "use lib" whith architecture and version specific dirs

While re-reading the documentation on use lib and looking through the directory structure again, I realise that all modules have ended up in either

lib/site_perl/5.005/
[download]

or in

lib/site_perl/5.005/i386-linux/
[download]

...and according to the documentation on use lib, a:

use lib "customers_perl_modules/lib/site_perl/5.005";
[download]

Should be enough, since directly underlying architecture-specific libs should be appended to @INC automagically.

...should be enough.

Let me try..

Yep, works!

But what happens when perl 5.6 gets installed?

/jeorgen

Comment on Re: "use lib" whith architecture and version specific dirs Select or Download Code

Replies are listed 'Best First'.
Re: Re: "use lib" whith architecture and version specific dirs by chipmunk (Parson) on Dec 11, 2000 at 08:29 UTC
The reason for version-specific directories is that a module compiled for one version of perl may not work with another version of perl; this is particularly true of modules with binary pieces. There may also be modules where the newer versions work with 5.6 but not 5.005, so you would install the newer version in site_perl/5.6 while leaving the old version in site_perl/5.005 unchanged. It's possible that none of these conflicts exist for any of the modules you're using, but you can play it safe by reinstalling all the site_perl modules when you upgrade to perl5.6.	[reply]
Re: Re: "use lib" whith architecture and version specific dirs by Fastolfe (Vicar) on Dec 11, 2000 at 08:03 UTC
When Perl 5.6 is installed, it'll need to look in 5.6.0 as well as 5.005 (assuming you let it look in the older place), and you'll need to update your paths to look in the 5.6.0 versions as well.	[reply]