There are many copies of JSON/PP.pm on the system, but my PERL5LIB is unset, so I think nothing is on @INC. I would think CPAN would not look at @INC anyway. Shouldn't it use only its local install directory? Surely allowing the same CPAN to be used with different library paths would lead to disaster! | [reply] |
my PERL5LIB is unset, so I think nothing is on @INC
Just dump @INC, so you don't have to guess:
perl -E 'say for @INC'
You don't use more than one perl version, do you?
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply]
[d/l] |
Silly me. Of course something is on my @INC, or I couldn't run perl. The first JSON:PP on my @INC is v2.24. But this doesn't explain why CPAN keeps seeing that instead of its own modules after doing an install. Does CPAN just assume that its own module directory is at the head of my @INC ? It isn't even there at all.
Which is even more mysterious, because if CPAN is finding JSON::PP on my @INC, it shouldn't find new modules at all after I install them, as they are in my CPAN directory and not on my @INC.
(To access modules that I install with CPAN, I have to change my PERL5LIB immediately before running perl, and change it back immediately afterwards, because of incompatibilities with our wrapper for git.)
| [reply] |
| [reply] |