From owner-freebsd-ports@FreeBSD.ORG Sat Jun 7 20:20:02 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 7BCECA3A for ; Sat, 7 Jun 2014 20:20:02 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4592E2E40 for ; Sat, 7 Jun 2014 20:20:01 +0000 (UTC) Received: from [76.184.156.59] ([76.184.156.59:59194] helo=[192.168.1.32]) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 26/75-11813-FE373935; Sat, 07 Jun 2014 20:20:00 +0000 Date: Sat, 07 Jun 2014 15:19:59 -0500 From: Paul Schmehl Reply-To: Paul Schmehl To: Torfinn Ingolfsen , FreeBSD Ports ML Subject: Re: How are ports built now Message-ID: <2AF4F1470E341E22BC76B4FD@Pauls-MacBook-Pro.local> In-Reply-To: References: 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.130:25 X-Authority-Analysis: v=2.1 cv=a+i+9CiF 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 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: Sat, 07 Jun 2014 20:20:02 -0000 --On June 7, 2014 at 10:04:17 PM +0200 Torfinn Ingolfsen wrote: > Hi, > > On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl > wrote: >> I'm an oldtimer, having used the port building system for years. >> Recently I upgraded two servers to 8.4 and implemented the pkgng system. >> Now, when I run portmaster -ad, it seems to keep reinstalling the same >> ports over and over again. >> >> Is portmaster not the appropriate method for updating ports with pkgng? >> Are we forced to now go to binary packages only? > > I think you are a bit confused here. AFAIK, portmaster, portupgrade > and so on are management tools for installing and upgrading ports. > However, to update the ports tree on your machine (which is what you > use when you are building from source) you need another tool. > Supported versions of FreeBSD have the portsnap(8) command, which is > used to update the ports tree. Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. I'm still trying to figure out what's wrong. I thought it might be some sort of conflict between the portmaster db and the pkgng db. 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