[sf-perl] upgrade hell?

[Fred Moyer]

I would suggest taking a look at the slides from Jeff's talk last
night, as it seems relevant to the issues you're experiencing. I wish
Stratopan had existing a year or two ago, I have spent a lot of time
on a few projects dealing with just these issues.

On Wed, Oct 31, 2012 at 8:49 AM, David Alban <extasia at extasia.org> wrote:
> thanks bryan,
>
> as you surmised, our cpan and home grown modules are installed in
> /nas/reg/lib/perl (symlink to /nas/reg/lib/perl5).  /nas/reg/ is a
> network filesystem mounted by all of our hosts.
>
> we include the statement:
>
>   use lib '/nas/reg/lib/perl';
>
> in all of our tools.  i'm not sure what to do in the case that's fast
> coming up:  the current hosts will continue running 5.8.8 but all of
> the new hosts will be running 5.10.1.  perhaps we do use a /nas/reg2/
> filesystem, complete with its own /nas/reg2/lib/perl (symlink to
> /nas/reg2/lib/perl5) and reinstall all cpan modules there for 5.10.1.
> and perhaps we change:
>
>   use lib '/nas/reg/lib/perl';
>
> in all of our tools to:
>
>   usr lib '/usr/local/lib/perl';
>
> and on the 5.8.8 hosts /usr/local/lib/perl is a symlink to
> /nas/reg/lib/perl and on the 5.10.1 hosts /usr/local/lib/perl is a
> symlink to /nas/reg2/lib/perl ?
>
> again, looking for perspectives from folks who've gone down this path
> and have had to maintain two versions of cpan modules and home grown
> tools which use them.
>
> On Tue, Oct 30, 2012 at 7:02 PM, Bryan Beeley <bryan at beeley.org> wrote:
>> I have faced something like this several times.  I have always installed
>> new versions of of CPAN modules without trouble, or having to muck with
>> with any of the defaults for library paths.
>>
>> However, if you have your libraries in a custom location, it might be
>> worth creating a new directory for the new modules, or moving the old
>> directory(ies?) aside, before you reinstall everything from CPAN (maybe
>> install the new modules in /nas/reg2).  I have always done this on
>> machines that have a default OS package install along with a custom
>> built Perl executable (usually built from source and installed in
>> /usr/local).  I would expect that using the default system Perl with a
>> custom directory for core libraries is more likely to cause trouble when
>> mixing versions.
>
> --
> Live in a world of your own, but always welcome visitors.
> ***
> Rule of law is for the little people.
> http://www.amazon.com/Liberty-Justice-Some-Equality-Powerful/dp/0805092056
> _______________________________________________
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm