From owner-freebsd-ports@FreeBSD.ORG Mon Feb 11 23:27:07 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 825E016A419 for ; Mon, 11 Feb 2008 23:27:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with SMTP id 3335B13C455 for ; Mon, 11 Feb 2008 23:27:06 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 1514 invoked by uid 399); 11 Feb 2008 23:27:06 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 11 Feb 2008 23:27:06 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <47B0D9C8.4080105@FreeBSD.org> Date: Mon, 11 Feb 2008 15:27:04 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Mark Ovens References: <479C872F.3000907@magichamster.com> <479D0000.7080206@FreeBSD.org> <47B08B18.6060804@magichamster.com> In-Reply-To: <47B08B18.6060804@magichamster.com> X-Enigmail-Version: 0.95.6 Content-Type: multipart/mixed; boundary="------------050409050702010007010906" Cc: freebsd-ports@freebsd.org Subject: Re: Portmaster ignoring +IGNOREME?? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2008 23:27:07 -0000 This is a multi-part message in MIME format. --------------050409050702010007010906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mark Ovens wrote: > Doug, it's happened again: It's impossible for me to debug this properly without knowing the command line options you used. I'm guessing from your description of the problem that you used at least -r and -u. > It honoured the +IGNOREME during the recursive ``make config'' but > failed during the build. If I understand the problem correctly, the attached patch will fix it. Please confirm this for me when you can. > This also highlights a potential problem with portmaster. because it > prints out all the pkg-message files at the end, and the summary list, > there is the potential for the reason for the abort to have scrolled out > of the shell's scrollback buffer (it wasn't far off in this instance) If you don't use -u, there is a pause between the end of the failed build and the display of the pkg-message files. If you do use -u it's assumed that you are able to handle the consequences of doing so. I actually suggest that people stop using -u, and I am seriously considering just removing it. It doesn't do what people apparently think it should do, and it's caused way more trouble than it's worth. Doug -- This .signature sanitized for your protection --------------050409050702010007010906 Content-Type: text/plain; name="pm-ignore-fix.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pm-ignore-fix.diff" --- portmaster 2008/01/30 01:40:33 2.24 +++ portmaster 2008/02/11 23:17:35 @@ -1811,7 +1811,7 @@ fi ;; esac - elif [ -n "$NO_RECURSIVE_CONFIG" ]; then + elif [ -n "$NO_RECURSIVE_CONFIG" -o -n "$URB_YES" ]; then echo '' echo "===>>> $upg_port has an +IGNOREME file, ignoring" echo '' --------------050409050702010007010906--