Perl Problem After Upgrade to 5.12.4

[Tim Daneliuk]

On 7/8/2011 8:39 AM, Jerry said this:
> On Fri, 08 Jul 2011 08:12:16 -0500
> Tim Daneliuk articulated:
> 
>> I was able to work around this by:
>>
>> 1) Uninstalling spamassassin and perl 5.12
>> 2) Upgrading to perl 5.14
>> 3) Running perl-after-upgrade
>> 4) Reinstalling spamassassin
> 
> That is not exactly the method prescribed in UPDATING:


You're right, of course - I ordinarily do this when I upgrade
perl ... somehow it slipped my tiny and aging mind.

Thanks for the reminder :)


> 
> <quote>
> 20110517:
>   AFFECTS: users of lang/perl*
>   AUTHOR: skv at FreeBSD.org
> 
>   lang/perl5.14 is out. If you want to switch to it from, for example
>   lang/perl5.12, that is:
> 
>   Portupgrade users:
>     0) Fix pkgdb.db (for safety):
>         pkgdb -Ff
> 
>     1) Reinstall new version of Perl (5.14):
>         env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\*
> 
>     2) Reinstall everything that depends on Perl:
>         portupgrade -fr perl
> 
>   Portmaster users:
>         portmaster -o lang/perl5.14 lang/perl5.12
> 
>         Conservative:
>         portmaster p5-
> 
>         Comprehensive (but perhaps overkill):
>         portmaster -r perl-
> 
>   Note: If the "perl-" glob matches more than one port you will need to
>         specify the name of the Perl directory in /var/db/pkg explicitly.
> 
> </quote>
> 
> I used the "portupgrade" method without incident. From what I have been
> told, "perl-after-upgrade" != "env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\*"
> 
> As always, YMMV!
> 


-- 
------------------------------------------------------------------------
Tim Daneliuk
tundra at tundraware.com