From owner-freebsd-ports@FreeBSD.ORG Fri Jun 11 20:45:30 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 74A6110656C0 for ; Fri, 11 Jun 2010 20:45:30 +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 AC0778FC1A for ; Fri, 11 Jun 2010 20:45:29 +0000 (UTC) Received: (qmail 16492 invoked by uid 399); 11 Jun 2010 20:45:28 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 11 Jun 2010 20:45:28 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C12A066.8020205@FreeBSD.org> Date: Fri, 11 Jun 2010 13:45:26 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Alberto Villa References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: portmaster: problem with --packages-build? 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: Fri, 11 Jun 2010 20:45:30 -0000 On 06/11/10 10:52, Alberto Villa wrote: > hi doug and list! > while upgrading libogg and libao (portmaster -x virtualbox -Rr libogg > libao) i've seen that some ports, which were already installed, got > reinstalled with a package. they're build dependencies of a port which > was upgraded, but they're also run dependencies of another one, The "build-only"ness of a port is calculated per portmaster run, so your results are not unexpected, even if they are not desirable. What needs to be done is to add code that tests whether ports marked build only for a given portmaster run are also listed as dependencies in an already installed port, but that's a non-trivial issue and my time right now is dominated by trying to find work, which unfortunately leaves little time available for portmaster hacking. My only suggestion (which admittedly is inadequate) is to apply the --delete-build-only knob on a case by case basis rather than having it in portmaster.rc. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/