Date: Fri, 15 Sep 2006 12:40:46 -0400 From: "Michael P. Soulier" <msoulier@digitaltorque.ca> To: freebsd-questions@freebsd.org Subject: Re: Poutupgrade unsafe Message-ID: <20060915164046.GN11663@tigger.digitaltorque.ca> In-Reply-To: <450A0E7F.5090400@voidcaptain.com> References: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th> <450A0E7F.5090400@voidcaptain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--quagH4H09id5XL2e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 14/09/06 Pete Slagle said: > This one bit me too, but we have only ourselves to blame; there was a > clear (well, pretty clear) warning of the change in /usr/ports/UPDATING. >=20 > You would never forget to check UPDATING before running portupgrade > would you? :) A nice portupgrade feature would be to grok UPDATING, and present you with = any such notes before the upgrade occurs. Mike --=20 Michael P. Soulier <msoulier@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein --quagH4H09id5XL2e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD4DBQFFCteOKGqCc1vIvggRAjZ6AJjJsjJQQM5PmuXU7MGAg4upkT6vAJ9vCe2B 4uBBpfzaGolRuGXj8JS5/Q== =//py -----END PGP SIGNATURE----- --quagH4H09id5XL2e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060915164046.GN11663>