Perl-Sensitive Sunglasses | |
PerlMonks |
Re^2: Puzzled by ppmby wrog (Friar) |
on Feb 28, 2012 at 00:06 UTC ( [id://956555]=note: print w/replies, xml ) | Need Help?? |
some searching seems to indicate that PPM itself (or at least the older pre-version-4 PPM) sets aside certain modules and makes sure to only load a given set of versions that are known to work together — best guess here is that when PPM runs, it messes with @INC so that the lib directory is in front of the site/lib directory so that it's sure of getting the versions that are known to work. Apparently, using the --precious flag will indeed do an install into the lib directory so that PPM will see it, but that
Things to try
If the first gives you 1.82 and the second gives you 1.48-r1, then you'll know that you're indeed getting the later version for ordinary code, the only way the earlier version is even seen is if you mess with @INC, and PPM is evidently messing with @INC and so you don't actually have to do anything (i.e., if you can live with PPM itself seeing the wrong version...) Or, if you're feeling adventurous you could try upgrade --precious on Archive::Tar and see what happens.
In Section
Seekers of Perl Wisdom
|
|