From owner-freebsd-ports  Thu Aug 21 15:36:14 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA24014
          for ports-outgoing; Thu, 21 Aug 1997 15:36:14 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA24008
          for <freebsd-ports@freebsd.org>; Thu, 21 Aug 1997 15:36:11 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53136(4)>; Thu, 21 Aug 1997 15:35:36 PDT
Received: by crevenia.parc.xerox.com id <177486>; Thu, 21 Aug 1997 15:35:26 -0700
From: Bill Fenner <fenner@parc.xerox.com>
To: asami@cs.berkeley.edu, fenner@parc.xerox.com
Subject: Re: Versioning bsd.port.mk
Cc: freebsd-ports@freebsd.org
Message-Id: <97Aug21.153526pdt.177486@crevenia.parc.xerox.com>
Date: Thu, 21 Aug 1997 15:35:17 PDT
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

We could create a bsd.port.mk target to rewrite the port Makefile (eek)
with bsd.port.mk's current version.  I can't think of any obvious way
to do something passively like the value in bsd.port.mk, since there's
no way to compare the dates without some reference of what was current
when the port was committed.

update-required-bsd.port.mk-version:
	mv Makefile Makefile.bak
	sed -e "s/NEED_MK_VERSION=.*/NEED_MK_VERSION=	${BSD_PORT_MK_VERSION}/" < Makefile.bak > Makefile

Or, the bsd.port.mk version requirement could be stored in a file in the
files/ directory -- I like this one less, since the Makefile is generally
the thing that creates the requirement for a certain version, but it's
certainly easier to maintain without worrying about spamming the Makefile
when trying to automatically update it.

  Bill