From owner-freebsd-ports@FreeBSD.ORG Tue Aug 4 18:35:10 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 EC0D5106564A for ; Tue, 4 Aug 2009 18:35:10 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [64.146.239.50]) by mx1.freebsd.org (Postfix) with ESMTP id BFE8E8FC0C for ; Tue, 4 Aug 2009 18:35:10 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from kstewart2.owt.com (kstewart2.owt.com [64.146.237.228]) (authenticated bits=0) by smtp.owt.com (8.13.8/8.13.8) with ESMTP id n74IYsFv015002; Tue, 4 Aug 2009 11:34:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=owt.com; s=default; t=1249410895; bh=yjrC1snzSBIY9MKMsTTtGwl7hN6Rm0FWEV2NiAl/ze0=; h=From:To:Subject:Date:Cc:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=GPJeKCoguLJc+ uHHbNGkj0n8VU/76dl6h38xgx5E7hSnf5KzlF/HRL13dIDOALMnn3Nbz9lZDiS8i73W 9XDqA/EJx3SZs8mcqhl9t1hWmkfC6H+C9iYcRopjv3qd2/8fwx9IDs24WQ6k2XH4ZnV WH6NKiwI48Xen6a5n8V3MzJk= From: Kent Stewart To: freebsd-ports@freebsd.org Date: Tue, 4 Aug 2009 11:34:53 -0700 User-Agent: KMail/1.9.10 References: <200908040750.n747ohUB021532@mp.cs.niu.edu> <4A7854B4.6050006@FreeBSD.org> In-Reply-To: <4A7854B4.6050006@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908041134.54086.kstewart@owt.com> Cc: Doug Barton , Scott Bennett , skv@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 18:35:11 -0000 On Tuesday 04 August 2009 08:33:08 am Doug Barton wrote: > 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. I had recently had problems moving packages from one fast computer to a slower one for installs. When I did the forced, recursive update of perl-5.10 using packages, there were ports only on the second computer that caused portupgrade to force load perl-5.8.*. Portupgrade, when it is forced, didn't pay attention to the registered conflicts. I had to delete the old version of perl and reinstall 5.10. IIRC, portmanager -s would show me the ports that were still linked to the old version of perl and could be compiled to upgrade on the slower computer. There were numerous "pkdgb -L" runs to re-establish the lost dependencies. Many were ports left behind by an incomplete removal of kde4 and simply deleting them got rid of most of the problems. I eventually got to where I could "portupgrade -Prf perl" and not have it compile anything or install an older version of perl. Tidy caused something similar and never was able to upgrade it and the programs that use it with portupgrade. Kent > > > hope this helps, > > Doug -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html