Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Feb 2005 12:24:07 +0100
From:      Dick Hoogendijk <dick@nagual.st>
To:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: Updated perl - broke stuff
Message-ID:  <20050214112407.GB7268@lothlorien.nagual.st>
In-Reply-To: <20050214023836.GA27431@xor.obsecurity.org>
References:  <200501271852.j0RIqQ9t010411@mp.cs.niu.edu> <44is5imspz.fsf@be-well.ilk.org> <04d201c51214$4bb07ab0$7702a8c0@officeeagle> <420FD249.4060408@mac.com> <2147483647.1108326906@[192.168.2.100]> <20050214023836.GA27431@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Feb Kris Kennaway wrote:
> On Sun, Feb 13, 2005 at 08:35:06PM -0600, Paul Schmehl wrote:
> > --On Sunday, February 13, 2005 5:18 PM -0500 Chuck Swiger <cswiger@mac.com> 
> > wrote:
> > >
> > >Did you read /usr/ports/UPDATING?  It contains a suggestion for how to
> > >update the Perl ports which might have helped...
> > >
> > Well, no.  Why on earth would I do *that*?  ;-)
> > 
> > (Thanks for the tip.  I ran it.)  I wonder why the perl port doesn't 
> > include  this command in a post-install script?
> 
> It's a once-off change needed when updating from an older version, and
> the post-install script (or any other part of the port build) doesn't
> know that this is what is happening.

Meaning I don't run this update script when updating perl from say
"5.8.5" to "5.8.6" ?
That all I have to do then is run "use.perl ports" ?

-- 
dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.11 ++ FreeBSD 5.3
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050214112407.GB7268>