From owner-freebsd-ports  Wed Aug 20 01:57:12 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA09789
          for ports-outgoing; Wed, 20 Aug 1997 01:57:12 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca13-16.ix.netcom.com [204.32.168.48])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA09784
          for <freebsd-ports@freebsd.org>; Wed, 20 Aug 1997 01:57:09 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA01189; Wed, 20 Aug 1997 01:56:15 -0700 (PDT)
Date: Wed, 20 Aug 1997 01:56:15 -0700 (PDT)
Message-Id: <199708200856.BAA01189@silvia.HIP.Berkeley.EDU>
To: itojun@itojun.org
CC: freebsd-ports@freebsd.org
In-reply-to: <6224.872066374@itojun.csl.sony.co.jp>
Subject: Re: ports/4326
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * 	how about one of the followings:
 * 	- timestamping (already rejected yesterday, I remember)

I think that's the right general direction to go (it has been proposed
many, many times already), but nobody figured out a way to implement
it....

 * 	- include latest bsd.port.mk into somewhere in /usr/ports
 * 	  (or somehow include bsd.port.mk to list of CVSup'ed files for
 * 	  collection "ports-all" ?)
 * 	  Then, we'll do
 * 	  # ln -s /usr/ports/somewhere/bsd.port.mk /usr/share/mk/bsd.port.mk

bsd.port.mk has branches, so it can't go into the ports tree.
Besides, you don't need the ports tree to build your own ports.

I think changing the fonts of the warning in the ports page, as well
as every single place that refers to cvsup'ing the ports tree might be 
the best solution.  Why is it so hard to understand, that the ports
tree is a moving target (like -stable or -current)? ;)

Satoshi