From owner-freebsd-ports  Thu Aug 21 15:53:30 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA25160
          for ports-outgoing; Thu, 21 Aug 1997 15:53:30 -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 PAA25152
          for <freebsd-ports@freebsd.org>; Thu, 21 Aug 1997 15:53:22 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53640(4)>; Thu, 21 Aug 1997 15:52:49 PDT
Received: by crevenia.parc.xerox.com id <177486>; Thu, 21 Aug 1997 15:52:43 -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.155243pdt.177486@crevenia.parc.xerox.com>
Date: Thu, 21 Aug 1997 15:52:39 PDT
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Or, the bsd.port.mk version requirement could be stored in a file in the
>files/ directory

Actually, this could be the most automated way of doing this, because you
could have a target like

${FILESDIR}/bsd_port_mk_version_required:	Makefile
	@echo ${BSD_PORT_MK_VERSION} > ${FILESDIR}/bsd_port_mk_version_required

so that any time the port Makefile gets updated, the version-required file
also gets updated.  This will end up creating version-required files with
higher versions than needed since, for example, they might get updated if
you just changed MASTER_SITES, but creating them automatically like this
takes a lot of the load off of porters.

  Bill