Re^3: Which takes priority site\lib or lib?

[moritz]

in reply to Re^2: Which takes priority site\lib or lib?
in thread Which takes priority site\lib or lib?

So they silently broke older installs

Well, old installations usually don't magically get a new perl. When installing a new major version of perl 5, it's a good idea to re-install all dependent modules anyway.

And it wasn't without warning either. To quote perl5120delta:

In @INC, ARCHLIB and PRIVLIB now occur after after the current version's site_perl and vendor_perl. Modules installed into site_perl>and vendor_perl will now be loaded in preference to those installed in ARCHLIB and PRIVLIB.

[BrowserUk]

Well, old installations usually don't magically get a new perl. When installing a new major version of perl 5,

But I wasn't installing a new version of Perl -- major or minor.

I was upgrading to a newer version of Test::More (from cpan) that is a (required) dependency of the module from cpan that I wanted to install; namely Inline::CPP.

And it wasn't without warning either.

I meant at install time. I'm using 5.10, why would I read the delta for 5.12?

Essentially, these new semantics means that even though I had an existing installation of Test::More in site\lib (which it could easily detect), it went ahead and silently installed the new version in lib; with the predictable result.

At least a heads up at install time would be nice. Better yet, the possibility to chose where it installed it. Better yet, detect the version of perl into which it is installing and chose the old semantics for pre-5.12 builds.