From owner-freebsd-ports@FreeBSD.ORG Sun Jun 8 15:54:16 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C4CAC897 for ; Sun, 8 Jun 2014 15:54:16 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4DD216C for ; Sun, 8 Jun 2014 15:54:15 +0000 (UTC) Received: from [76.184.156.59] ([76.184.156.59:59973] helo=[192.168.1.32]) by dnvrco-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 22/94-23145-02784935; Sun, 08 Jun 2014 15:54:09 +0000 Date: Sun, 08 Jun 2014 10:54:08 -0500 From: Paul Schmehl Reply-To: Paul Schmehl To: Kevin Phair , FreeBSD Ports Subject: Re: How are ports built now Message-ID: In-Reply-To: <5394837D.80901@gmail.com> References: <20140607202241.GA59544@spectrum.skysmurf.nl> <53938114.9060303@gmx.de> <5394837D.80901@gmail.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-RR-Connecting-IP: 107.14.64.142:25 X-Authority-Analysis: v=2.1 cv=Y7x2s3uN c=1 sm=1 tr=0 a=iy4Q/FHRRDrLt+awqfk3Bw==:117 a=iy4Q/FHRRDrLt+awqfk3Bw==:17 a=ayC55rCoAAAA:8 a=05ChyHeVI94A:10 a=kj9zAlcOel0A:10 a=pGLkceISAAAA:8 a=UdvEN9gbqWsBAELrqE0A:9 a=CjuIK1q_8ugA:10 a=MSl-tDqOz04A:10 a=_RhRFcbxBZMA:10 X-Cloudmark-Score: 0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2014 15:54:16 -0000 --On June 8, 2014 at 11:38:37 AM -0400 Kevin Phair wrote: > > On 6/8/14, 11:20 AM, Paul Schmehl wrote: >> --On June 7, 2014 at 11:16:04 PM +0200 olli hauer wrote: >> >>> >>> >>> Do you see which port is looping? >>> Perhaps a port was moved / renamed / removed and portmaster therfore is >>> looping around >>> >>> Sadly I cannot help more since I used all the years tinderbox / >>> poudriere >>> to build packages. >>> >> >> I've been working on this for two days now, so the parameters have >> changed a bit. But here's an example of what prompted my question: >> >> This is the result of portmaster -ad >> >> ===>>> All >> (18) >> >> [[stuff]] >> >> ===>>> Proceed? y/n [y] n >> >> This is the result of pkg upgrade -n >> >> # pkg upgrade -n >> Updating repository catalogue >> Upgrades have been requested for the following 150 packages: >> >> [[different stuff]] >> The upgrade will require 426 MB more space >> >> 373 MB to be downloaded >> >> Clearly portmaster and pkg upgrade disagree on what work needs to be >> done. >> > Do you have non-default port options configured? I believe the packages > are all created with the default options, so that if you've installed > everything from ports, and some of those ports with non-default options, > your dependencies when upgrading with portmaster could end up looking > different than when upgrading with pkg. Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell