develooper Front page | perl.perl5.porters | Postings from April 2010

RE: deprecation and install destinations

Thread Previous | Thread Next
From:
Jan Dubois
Date:
April 27, 2010 16:01
Subject:
RE: deprecation and install destinations
Message ID:
0bb201cae65d$9d91de50$d8b59af0$@activestate.com
On Tue, 27 Apr 2010, Todd Rinaldo wrote:
> When discussing module deprecations earlier this year, it came up that
> dual life modules installed from CPAN should not set INSTALLDIRS to
> perl. Instead, the CPAN instance of the module should install to the
> site_lib tree. Is this correct?
>
> I notice version.pm from CPAN is installing to site_lib under 5.12
> perl. It's the only dual life module that does. Is this a mistake or
> are there reasons it needs to do this?

Starting with 5.12 site_lib comes before privlib in @INC, so I would think
*all* modules on CPAN should install into site_lib for 5.12 and later and
not overwrite the version in privlib.

The new version will always take precedence in @INC, and it is easy to
revert to the bundled version by removing the new code in site_lib.

This didn't work in earlier Perl versions because site_lib used to be
shadowed by privlib, and dual-life modules had to go to extra efforts
to be updateable.

Cheers,
-Jan


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About