From owner-freebsd-ports  Sat May 17 11:13:08 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA04968
          for ports-outgoing; Sat, 17 May 1997 11:13:08 -0700 (PDT)
Received: from nexis.net (customer-1.ican.net [198.133.36.101])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04963
          for <freebsd-ports@FreeBSD.ORG>; Sat, 17 May 1997 11:13:06 -0700 (PDT)
Received: from localhost (james@localhost)
	by nexis.net (8.8.5/8.8.5) with SMTP id OAA01330;
	Sat, 17 May 1997 14:07:22 -0400 (EDT)
Date: Sat, 17 May 1997 14:07:21 -0400 (EDT)
From: James FitzGibbon <james@nexis.net>
To: Narvi <narvi@haldjas.folklore.ee>
cc: Satoshi Asami <asami@vader.cs.berkeley.edu>, freebsd-ports@FreeBSD.ORG
Subject: Re: bsd.port.mk
In-Reply-To: <Pine.BSF.3.96.970517204613.16511A-100000@haldjas.folklore.ee>
Message-ID: <Pine.BSF.3.95q.970517140623.1036D-100000@nexis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 17 May 1997, Narvi wrote:

> No! No! NO!
> 
> Yes, it would be great. But I didn't mean something as complex.
> 
> What I meant is just keeping a copy of the bsd.port.mk file in the "root"
> directory of the ports (which for some people is /usr/ports). 
> 
> It would make it real easy for people to copy it over to the right place
> (/usr/share/mk) or make /usr/share/mk/bsd.ports.mk a link to the one in
> the directory they sup/cvsup ports to.

That makes sense.  Basically, so that when someone says "It doesn't work!"
we can say "Copy /usr/ports/bsd.port.mk over to /usr/share/mk" instead of
"Well, you have to learn how to CVsup so that you can get a newer copy of
bsd.port.mk".

Works for me.

--
j.