From owner-freebsd-ports  Wed Oct  7 15:52:13 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA13823
          for freebsd-ports-outgoing; Wed, 7 Oct 1998 15:52:13 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13817
          for <ports@freebsd.org>; Wed, 7 Oct 1998 15:52:12 -0700 (PDT)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca3-63.ix.netcom.com [209.109.233.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA19472; Wed, 7 Oct 1998 15:52:07 -0700 (PDT)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA11465; Wed, 7 Oct 1998 15:52:04 -0700 (PDT)
Date: Wed, 7 Oct 1998 15:52:04 -0700 (PDT)
Message-Id: <199810072252.PAA11465@silvia.hip.berkeley.edu>
To: n@nectar.com
CC: ports@FreeBSD.ORG
In-reply-to: <E0zR2HD-0000Gl-00@spawn.nectar.com> (message from Jacques
	Vidrine on Wed, 07 Oct 1998 17:41:47 -0500)
Subject: Re: What's the right way to handle old bsd.port.mk?
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

 * OK, one more thing.  As far as I know, updating bsd.port.mk
 * will require end users to do one of the following:
 * 
 * * cvsup and install bsd.port.mk from src/share/mk
 * * use cvsweb.cgi to download the correct revision of bsd.port.mk
 * * grab either 
 *     ftp://ftp.freebsd.org/pub/FreeBSD-stable/src/share/mk/bsd.port.mk OR
 *     ftp://ftp.freebsd.org/pub/FreeBSD-current/src/share/mk/bsd.port.mk
 *   depending 
 * 
 * Seems like the latter is probably easiest for most users.  Can you
 * think of any snafus or better alternatives before I write something
 * up saying ``do this to stay in sync with the ports collection''?

That sounds fine, but for -stable, they may need more than just
bsd.port.mk (especially if they are using something older than
2.2.7R).  There's an "minimal upgrade kit" linked from the
www.freebsd.org/ports page.

The biggest problem here is that people are installing 2.2.7R and
thinking they can immediately use the latest ports-current (because
that is the latest release).  We need to find why they are thinking
that way and fix it.

Right now -current and 3.0-snap users are not much of a problem
because they generally know what it takes to track -current, but with
3.0R coming up, we should make sure those users won't get the same bad
idea.

Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message