From owner-freebsd-ports@FreeBSD.ORG Tue Aug 4 15:33:16 2009 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 84A48106566B for ; Tue, 4 Aug 2009 15:33:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id D0B4B8FC0A for ; Tue, 4 Aug 2009 15:33:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 1652 invoked by uid 399); 4 Aug 2009 15:33:14 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 4 Aug 2009 15:33:14 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A7854B4.6050006@FreeBSD.org> Date: Tue, 04 Aug 2009 08:33:08 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.22 (X11/20090729) MIME-Version: 1.0 To: Scott Bennett References: <200908040750.n747ohUB021532@mp.cs.niu.edu> In-Reply-To: <200908040750.n747ohUB021532@mp.cs.niu.edu> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: skv@freebsd.org, freebsd-ports@freebsd.org Subject: Re: recent update causes perl5.10 build failure 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: Tue, 04 Aug 2009 15:33:16 -0000 Scott Bennett wrote: > Keep in mind that this experience did appear to reveal a portmaster bug. > After the "portmaster -w -v -a" had already asked whether to rebuild perl5.8 > even though it had a +IGNOREME file and had gotten an enter key in response, > which should have selected the "n" shown as the default ("[n]"), it later > went ahead and built perl5.8 anyway. From what you and the documentation > have told me, that should never happen. I don't think it can happen if the build of all the dependencies is under portmaster's control. However there are edge cases when dependencies don't show up when portmaster polls the port for the list but the ports infrastructure builds them anyway. I'd have to look at a log of the whole session to be sure. Having both perl5.8 and perl5.10 installed at the same time is kind of an odd configuration, and could very well produce the kind of edge case I described above. hope this helps, Doug -- This .signature sanitized for your protection