From owner-freebsd-ports  Fri Aug 22 09:45:35 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA18534
          for ports-outgoing; Fri, 22 Aug 1997 09:45:35 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA18529
          for <ports@freebsd.org>; Fri, 22 Aug 1997 09:45:32 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0x1wpq-00052M-00; Fri, 22 Aug 1997 10:45:18 -0600
To: asami@cs.berkeley.edu (Satoshi Asami)
Subject: Re: Versioning bsd.port.mk 
Cc: fenner@parc.xerox.com, ports@freebsd.org
In-reply-to: Your message of "Fri, 22 Aug 1997 04:00:39 PDT."
		<199708221100.EAA06524@silvia.HIP.Berkeley.EDU> 
References: <199708221100.EAA06524@silvia.HIP.Berkeley.EDU>  
Date: Fri, 22 Aug 1997 10:45:17 -0600
From: Warner Losh <imp@rover.village.org>
Message-Id: <E0x1wpq-00052M-00@rover.village.org>
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199708221100.EAA06524@silvia.HIP.Berkeley.EDU> Satoshi
Asami writes: 
: Actually, looking at yours and itojun's patch, I was wondering...can
: we use the date in the $Id$ field in the port's Makefile?  We should
: make it just a warning (because there just may be no newer
: bsd.port.mk) but this is zero additional burden for the port
: committers and probably enough information for clueless users to get
: the latest bsd.port.mk if something goes wrong.

Hmmm.  I'm not sure that that is even foolproof.  If you are making
changes to the bsd.port.mk file while I'm making changes to the
gerbils port.  My changes get in first, and then yours.  My changes
depend on version n-1 of the bsd.port.mk file, but version n breaks
it.  I'd not get a warning, and it wouldn't work.  This may be an
acceptible race to have, but something strikes me as wrong here for
some reason.

Warner