From owner-freebsd-ports@FreeBSD.ORG Thu Sep 9 00:25:08 2010 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 3F6C810656C4 for ; Thu, 9 Sep 2010 00:25:08 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.41]) by mx1.freebsd.org (Postfix) with ESMTP id 1BE918FC13 for ; Thu, 9 Sep 2010 00:25:07 +0000 (UTC) Received: (qmail 18079 invoked from network); 9 Sep 2010 00:25:07 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 9 Sep 2010 00:25:07 -0000 Message-ID: <4C882966.5070908@telenix.org> Date: Wed, 08 Sep 2010 20:25:10 -0400 From: Chuck Robey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100907 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4C75C308.5060506@telenix.org> <4C75F8F9.3060704@DataIX.net> <4C88030C.1030505@telenix.org> <20100908181535.0bb7d329@seibercom.net> In-Reply-To: <20100908181535.0bb7d329@seibercom.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: portmanager endlessly looping in x11 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: Thu, 09 Sep 2010 00:25:08 -0000 On 09/08/10 18:15, Jerry wrote: > Portmanager did have a nasty bug that involved looping. It was fixed > ages ago though. Are you running the latest version; i.e., "0.4.1_9" on > your system? Run "portmanager -v" to confirm. > > Without the '-p' option, portmanager only looks 1 level deep. with the > '-p' option, it will search the entire dependency chain. I always use > the '-p' option and never experience any problems described by you. > Not sure if the -p does that or not, but I *did* read (more than just a few times) about the -p (meaning "pristine") option, and from the reading, it doesn't tell me that it might affect looping, and I didn't see anything about it in the man page. I didn't just try it and immediately mail, I tried to DTRT. Doesn't matter too much to me now, because I really love the fact that I did 4 *very* large (meaning lengthy dependency lists) ports, with 100% 1st-time accuracy, which means I will stay with portmaster for sure now. Also, because those ports are now all installed, and I don't want to take a few days to rebuild everything all over again. It looks like, in the default case, portmanager detects more problems than it deals with, which is not a desirable default action. It's probably a needed default action for some use case ... do you happen to know what that is?