Date: Tue, 9 Nov 2004 11:02:40 +0000 From: Andy Smith <andy@freebsdwiki.org> To: freebsd-stable@freebsd.org Subject: Re: Portupgrade script. Message-ID: <20041109110240.GI1549@caffreys.strugglers.net> In-Reply-To: <20041109103902.GA69223@kierun.org> References: <20041109103902.GA69223@kierun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--zi2eTBhaeOcYgKgV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 09, 2004 at 10:39:02AM +0000, Yann Golanski wrote: > Would people be kind enough to have a look at the following script and > tell me what horrors/faux pas/stupid things I have done? =20 >=20 > The script is an almost automated way to upgrade all your ports to the > latest version.=20 Without looking further I'd say this is a bad idea because sometimes an upgrade to a port radically changes its functionality or does something else inconvenient. For example, upgrading databases/mysql*-server will shut down a running mysql server. You need to be manually reading /usr/ports/UPDATING before each update. What I tend to do is automate the cvsup and then email a report of what could be upgraded. The actual upgrades are done semi-automatically with a portupgrade -arR after checking it isn't going to do anything untoward. --zi2eTBhaeOcYgKgV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBkKPQIJm2TL8VSQsRAneRAKCr34CfabeTefp0Tq3vFs6R6R9A9wCg7QP8 jpo+NpQmjLtgAyPv8IfSNPE= =IwWo -----END PGP SIGNATURE----- --zi2eTBhaeOcYgKgV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041109110240.GI1549>