From owner-freebsd-ports Sat Sep 9 8:16: 8 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 982D937B42C; Sat, 9 Sep 2000 08:15:58 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id SAA08438; Sat, 9 Sep 2000 18:15:55 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e899Whj07248; Sat, 9 Sep 2000 12:32:43 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39BA03B9.E3C051C5@FreeBSD.org> Date: Sat, 09 Sep 2000 12:32:41 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kris Kennaway Cc: asami@FreeBSD.org, ports@FreeBSD.org Subject: Re: Extending bsd.port.mk diagnostics when some of the patches failto apply [patch for review] References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway wrote: > On Mon, 4 Sep 2000, Maxim Sobolev wrote: > > > I'm sure all hardcore porters are aware of this problem: when you are trying to > > update some port and not all patches applied cleanly there is no easy way to > > figure from error message which patches have been applied and which one has > > not. The following patch is expected to make a life of porter a bit easier by > > extending verbosity of error messages in this case (it doesn't affect anything > > if all patches were applied cleanly). > > Looks good! Satosi, Please tell your final word! ;) -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message