From owner-freebsd-ports  Wed Mar  3  3:20:33 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from dfw-ix15.ix.netcom.com (dfw-ix15.ix.netcom.com [206.214.98.15])
	by hub.freebsd.org (Postfix) with ESMTP id 4E7DD15370
	for <ports@freebsd.org>; Wed,  3 Mar 1999 03:19:51 -0800 (PST)
	(envelope-from asami@silvia.hip.berkeley.edu)
Received: (from smap@localhost)
          by dfw-ix15.ix.netcom.com (8.8.4/8.8.4)
	  id FAA19105 for <ports@freebsd.org>; Wed, 3 Mar 1999 05:19:33 -0600 (CST)
Received: from sji-ca7-236.ix.netcom.com(209.109.235.236) by dfw-ix15.ix.netcom.com via smap (V1.3)
	id rma019087; Wed Mar  3 05:18:57 1999
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id DAA59993; Wed, 3 Mar 1999 03:18:53 -0800 (PST)
Date: Wed, 3 Mar 1999 03:18:53 -0800 (PST)
Message-Id: <199903031118.DAA59993@silvia.hip.berkeley.edu>
X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@silvia.hip.berkeley.edu using -f
To: ports@freebsd.org
Subject: configure patches
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

It was brought to my attention that some of the recent "for
4.0-current" fixes have done in haste and without regards of the
Y2.001k problem (which is the branch date for 5.0-current).

Specifically, if you have a configure that looks like this:

  freebsd3*)
    foo bar baz

then don't change it to

  freebsd[34]*)
    foo bar baz

but try something like

  freebsd[3-9]*)
    foo bar baz

or even

  freebsd*)
    foo bar baz

depending on what other cases are around it.

That way we won't have to do the same thing all over again when the
next branch rolls around.  Thanks!

Satoshi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message