From owner-freebsd-questions@FreeBSD.ORG Fri Sep 15 16:41:01 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B715516A407 for ; Fri, 15 Sep 2006 16:41:01 +0000 (UTC) (envelope-from msoulier@digitaltorque.ca) Received: from mail.storm.ca (mail.storm.ca [209.87.239.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98A9E43D6A for ; Fri, 15 Sep 2006 16:40:54 +0000 (GMT) (envelope-from msoulier@digitaltorque.ca) Received: from tigger.digitaltorque.ca (hs-216-106-102-70.storm.ca [216.106.102.70]) by mail.storm.ca (8.13.6+Sun/8.13.6) with ESMTP id k8FGepD5015414 for ; Fri, 15 Sep 2006 12:40:52 -0400 (EDT) Received: by tigger.digitaltorque.ca (Postfix, from userid 500) id 706E111EE2F; Fri, 15 Sep 2006 12:40:46 -0400 (EDT) Date: Fri, 15 Sep 2006 12:40:46 -0400 From: "Michael P. Soulier" To: freebsd-questions@freebsd.org Message-ID: <20060915164046.GN11663@tigger.digitaltorque.ca> Mail-Followup-To: freebsd-questions@freebsd.org References: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th> <450A0E7F.5090400@voidcaptain.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="quagH4H09id5XL2e" Content-Disposition: inline In-Reply-To: <450A0E7F.5090400@voidcaptain.com> User-Agent: Mutt/1.4.2.1i Subject: Re: Poutupgrade unsafe X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 16:41:01 -0000 --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 "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--