Date: Thu, 15 Jan 1998 22:20:19 -0800 (PST) From: asami@cs.berkeley.edu (Satoshi Asami) To: ache@nagual.pp.ru Cc: ports@FreeBSD.ORG Subject: Re: bsd.port.mk patch for review Message-ID: <199801160620.WAA02177@bubble.didi.com> In-Reply-To: <Pine.BSF.3.96.980116084914.20775A-100000@lsd.relcom.eu.net> (message from =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= on Fri, 16 Jan 1998 08:54:55 %2B0300 (MSK))
next in thread | previous in thread | raw e-mail | index | archive | help
* 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801160620.WAA02177>