HEADS UP: /usr/ports/UPDATING documents upgrade pitfalls
kris at obsecurity.org
Mon Mar 1 14:38:57 PST 2004
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.
----- Forwarded message from Kris Kennaway <kris at FreeBSD.org> -----
X-Original-To: kkenn at localhost
Delivered-To: kkenn at localhost.obsecurity.org
Delivered-To: kris at freebsd.org
Delivered-To: ports-committers at freebsd.org
From: Kris Kennaway <kris at FreeBSD.org>
Date: Mon, 1 Mar 2004 14:34:22 -0800 (PST)
To: ports-committers at FreeBSD.org, cvs-ports at FreeBSD.org,
cvs-all at FreeBSD.org
Subject: cvs commit: ports UPDATING
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.16.4
kris 2004/03/01 14:34:22 PST
FreeBSD ports repository
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.
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.
Revision Changes Path
1.1 +31 -0 ports/UPDATING (new)
----- End forwarded message -----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040301/9af0d8f9/attachment.bin
More information about the freebsd-ports