From owner-freebsd-ports Sun Jan 18 17:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06424 for freebsd-ports-outgoing; Sun, 18 Jan 1998 17:23:41 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06409; Sun, 18 Jan 1998 17:23:26 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id RAA17475; Sun, 18 Jan 1998 17:23:19 -0800 (PST) (envelope-from jdp) Message-Id: <199801190123.RAA17475@austin.polstra.com> To: ache@nagual.pp.ru Subject: Re: amanda port, empty PATCH_STRIP= lines causes trouble In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: ports@FreeBSD.ORG, asami@FreeBSD.ORG Date: Sun, 18 Jan 1998 17:23:19 -0800 From: John Polstra Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= wrote: > The first reason of "unfixing" was that standard ncurses patches > set applies cleanly on all systems excepting FreeBSD (which have > abnormal "fixed" patch). Come on, Andrey, the new patch has broken a sizeable portion of the ports tree just to fix ncurses, which IMHO is broken itself. > Ncurses patches set is only bug trigger and it seems better not wait > until another one comes in. When another one comes in, then we'll have two. Currently, we have a lot more broken ports than that, all as a result of this change. > I especially wonder why you not say something when patch was "fixed" > first and new CVS imported. Sometimes the consequences of a change aren't obvious until it's been made. This one is bad news. A lot of people are complaining about it. I wish you'd just back it out until a better solution can be found. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth