From owner-freebsd-ports Sun Jan 18 21:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27865 for freebsd-ports-outgoing; Sun, 18 Jan 1998 21:53:03 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27859; Sun, 18 Jan 1998 21:52:53 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id IAA16486; Mon, 19 Jan 1998 08:52:11 +0300 (MSK) (envelope-from ache) Date: Mon, 19 Jan 1998 08:52:07 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Peter Wemm cc: Satoshi Asami , perhaps@yes.no, gpalmer@FreeBSD.ORG, ports@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: amanda port, empty PATCH_STRIP= lines causes trouble In-Reply-To: <199801190205.KAA23505@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 19 Jan 1998, Peter Wemm wrote: > I agree with Satoshi. My preference would be to convert the new patch to > a port, revert to the old patch in the tree (with it's "unique" handling > of Index:), and leave the change to cvs in place. Once we've had a -stable > release with a cvs that generates full paths in the diff headers and > people have had a chance to upgrade/make world/etc, then we can revisit > replacing the patch in the base tree. 1) Lets deal with -stable first because of its results depends how -current import of new patch should be treated. Dealing with -stable not depends of -current new patch but not vice versa. 2) About -stable. Why not make _separate_ version of patch with its "unique" Indexes: handling? I.e. we can have right "/usr/bin/patch" in the base system and "/usr/bin/broken_patch" for ports. It will be one-line change in bsd.port.mk -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/