Date: Fri, 20 May 2011 20:11:26 +0200 (CEST) From: Henk van Oers <henk@signature.nl> To: freebsd-ports@freebsd.org Cc: rotkaps_spam_trap@gmx.de Subject: Re: New perl, why not: perl-after-upgrade (Heino Tiedemann) Message-ID: <alpine.BSF.2.00.1105202004100.75179@dee.signature.nl> In-Reply-To: <20110519120031.59C2A1065678@hub.freebsd.org> References: <20110519120031.59C2A1065678@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Please join perl@freebsd.org On Thu, 19 May 2011, freebsd-ports-request@freebsd.org wrote: > Today's Topics: > 19. New perl, why not: perl-after-upgrade (Heino Tiedemann) > > ------------------------------ > > Message: 19 > Date: Thu, 19 May 2011 10:30:13 +0200 > From: Heino Tiedemann <rotkaps_spam_trap@gmx.de> > Subject: New perl, why not: perl-after-upgrade > To: freebsd-ports@freebsd.org > Message-ID: <l11fa8-tne.ln1@news.hansenet.de> > Content-Type: text/plain; charset=us-ascii > > Hi, > > Is there e reason why in ports/UPDATING is this mentioned: > > ,----[ 20110517 ] > | 0) Fix pkgdb.db (for safety): pkgdb -Ff > | 1) Reinstall new version of Perl (5.14): env DISABLE_CONFLICTS=1 portupgrade ... > | 2) Reinstall everything that depends on Perl: ... > `---- > > > and not this: > > ,----[ man perl-after-upgrade ] > | The standard procedure after a perl port (lang/perl5.X) upgrade is to > | basically reinstall all other packages that depend on perl. This is > | always a painful exercise. The perl-after-upgrade utility makes this > | process mostly unnecessary. > `---- > > > Heino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1105202004100.75179>