From owner-freebsd-ports Tue Jan 14 04:12:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA09293 for ports-outgoing; Tue, 14 Jan 1997 04:12:41 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA09285 for ; Tue, 14 Jan 1997 04:12:36 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id NAA10057; Tue, 14 Jan 1997 13:10:53 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id NAA00518; Tue, 14 Jan 1997 13:11:26 +0100 (MET) Message-Id: <3.0.32.19970114131125.00a753f0@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 14 Jan 1997 13:11:26 +0100 To: asami@vader.cs.berkeley.edu (Satoshi Asami) From: Eivind Eklund Subject: Re: AfterStep in -current Cc: ports@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:09 AM 1/14/97 -0800, Satoshi Asami wrote: > * Perhaps it would be an idea for ports to specify minimum version of > * bsd.ports.mk? (Just set it to whatever the author of the port has on his > * system - better that too many people upgrade than too few.) > >I don't think that is necassary, and it will be a royal pain to keep >track for the whole ports tree. Why is it nescarry to keep track? I suggest just copying the version number from the version the port author is running to somewhere in the port, and just let that be a minimum. No changes until the port is 'naturally updated', whereupon people might again be required to update bsd.ports.mk. >I really don't want to add another mandatory variable to every single one of >our 752 ports. Default to no version requirement. No need to update old ports. >Besides, the ports tree is only tracking -current, in principle. If >you have an old system, you should always get the latest bsd.port.mk >(and put it in /usr/share/mk :) and try your luck, as we still cannot >guarantee anything. Of course. The point of this was to make it easier to avoid spurious bug-reports of the type I gave. Not a pet idea of mine; just something I thought might save _you_ some work. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/