From owner-freebsd-ports Thu Jan 15 22:20:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01620 for freebsd-ports-outgoing; Thu, 15 Jan 1998 22:20:42 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from bubble.didi.com (granlibakken-250.sierra.net [207.135.219.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01604 for ; Thu, 15 Jan 1998 22:20:34 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.8) id WAA02177; Thu, 15 Jan 1998 22:20:19 -0800 (PST) (envelope-from asami) Date: Thu, 15 Jan 1998 22:20:19 -0800 (PST) Message-Id: <199801160620.WAA02177@bubble.didi.com> To: ache@nagual.pp.ru CC: ports@FreeBSD.ORG In-reply-to: (message from =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= on Fri, 16 Jan 1998 08:54:55 +0300 (MSK)) Subject: Re: bsd.port.mk patch for review From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * No, I mean patch 2.5 only (-current), not patch 2.1 (-stable) You mean 3.0-current and 2.2-stable. I am not worried about 2.1-stable too much, we don't support it officially anymore anyway. * -b works differently between this two versions. * * In case you want the same bsd.port.mk in both -current and -stable, * some trick must be used to detect patch version, maybe * 'patch --version' call or just simple -current detection, * or adding PATCHFLAGS to sys.mk, etc. We can have different bsd.port.mk for -current and 2.2, but I'd like to avoid that. Yes, we can certainly fix this in bsd.port.mk but I think this just illustrates that it's patch that really needs to be fixed. Can we tell POSIX to go fsck itself and make patch work the same on all versions of FreeBSD? Satoshi