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

Re: deprecation and install destinations

Thread Previous
From:
Michael G Schwern
Date:
May 8, 2010 12:40
Subject:
Re: deprecation and install destinations
Message ID:
4BE5BE1B.4070102@pobox.com
On 2010.4.27 4:01 PM, Jan Dubois wrote:
> 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.

This is all correct.

The hanging issue in the discussion last year was how best to implement this
in dual-life CPAN modules.  AFAIK it was left at just having the authors write
the logic themselves rather than having the build system second guess their
installdirs setting.


-- 
Stabbing you in the face for your own good.

Thread Previous


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