[REPOST] problem upgrading perl

[Jim Trigg]

On Tue, Jun 16, 2009 at 11:44:54PM -0500, Scott Bennett wrote:
>      On Tue, 16 Jun 2009 20:07:26 +0200 Alexey Shuvaev
> <shuvaev at physik.uni-wuerzburg.de> wrote:
> >Hmmm... Looking at portmaster sources I've got one idea.
> >Can you try more precise command to upgrade everything depending on perl?
> >
> >nice +18 portmaster -v -r perl-threaded-5.10.0_3
> >
> >The point is that perl\* wildcard gives you both perl-threaded-XXX and
> >perltidy-XXXX which might be bad idea.
> 
>      Bingo!!  Very nice call.  It has now driven me to distraction with dialog
> boxes for configuration stuff for many ports/packages, and is now busily
> reinstalling perl intself.
> >
> >If this is the case I think UPDATING entry should be improved
> >to use perl-\* wildcard.
> 
>      I think you meant to *not* use the wildcard, and yes, /usr/ports/UPDATING
> is clearly wrong in this case and should be fixed.
>      Thanks very much for solving this.  I still have to deal with some
> problems with options on the various packages/ports to be updated, but I can
> proceed for now.

Actually, he was suggesting changing from perl\* to perl-\* so it would
only match the perl port.  Unfortunately, that won't work as there is at
least one other port that will match that -- net/p5-perl-ldap (portname
perl-ldap).  So it should be revised to instruct users to use the exact
portname in /var/db/pkg.

Jim
-- 
Jim Trigg, Lord High Everything Else  O-      /"\
                                              \ /  ASCII RIBBON CAMPAIGN
Hostmaster, Huie Kin family website            X    HELP CURE HTML MAIL
Verger, All Saints Church - Sharon Chapel     / \