From owner-freebsd-questions@FreeBSD.ORG Mon Mar 1 14:38:57 2004 Return-Path: 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 19AC316A4CE; Mon, 1 Mar 2004 14:38:57 -0800 (PST) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DFCE43D2D; Mon, 1 Mar 2004 14:38:57 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (02e11380d6ffb766c88cdbfdaae7919d@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i21McuTw010327; Mon, 1 Mar 2004 14:38:56 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DA54D511DC; Mon, 1 Mar 2004 14:38:55 -0800 (PST) Date: Mon, 1 Mar 2004 14:38:55 -0800 From: Kris Kennaway To: ports@FreeBSD.org Message-ID: <20040301223855.GA4591@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: questions@FreeBSD.org Subject: HEADS UP: /usr/ports/UPDATING documents upgrade pitfalls X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2004 22:38:57 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable FYI..everyone should get in the habit of checking this file for changes after they update their ports tree. In particular, the inaugural entry addresses the problems many people have experienced when trying to upgrade portupgrade. Kris ----- Forwarded message from Kris Kennaway ----- X-Original-To: kkenn@localhost Delivered-To: kkenn@localhost.obsecurity.org Delivered-To: kris@freebsd.org Delivered-To: ports-committers@freebsd.org From: Kris Kennaway Date: Mon, 1 Mar 2004 14:34:22 -0800 (PST) To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports UPDATING X-FreeBSD-CVS-Branch: HEAD Precedence: bulk X-Loop: FreeBSD.ORG X-UIDL: oIA!!79=3D!!MWa"!NhO!! X-Bogosity: No, tests=3Dbogofilter, spamicity=3D0.000000, version=3D0.16.4 kris 2004/03/01 14:34:22 PST FreeBSD ports repository Added files: . UPDATING=20 Log: Add an UPDATING file that will be used to document additional steps that users may need to perform when updating their ports collection. The intent is similar to the /usr/src/UPDATING file. =20 Kick it off with a description of how to update past the ruby 1.6->1.8 changeover on i386, cribbed from knu's commit message. =20 Revision Changes Path 1.1 +31 -0 ports/UPDATING (new) http://cvsweb.FreeBSD.org/ports/UPDATING?rev=3D1.1&content-type=3Dtext/plain ----- End forwarded message ----- --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAQ7t+Wry0BWjoQKURAq9DAJwM7mhCungJTHbjm++eTptZf/mUsQCeOrky gqhGHuCW8eNKpE5of/iBT6g= =P0au -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe--