From owner-freebsd-ports@freebsd.org Sat Dec 17 15:24:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1AD9C852F5 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9F1542F2 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 9B964C852F4; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99634C852F3 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D2212F1 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id D2B4D43C0B; Sat, 17 Dec 2016 09:23:05 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , mueller6722@twc.com Subject: The ports collection has some serious issues Message-ID: Date: Sat, 17 Dec 2016 09:24:14 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 15:24:16 -0000 From Thomas Mueller: >> From John Marino: >> Starting with a clean system: 1) install synth from binary package >> from official freebsd builder (a single >> package) 2) Configure synth if necessary 3) command synth to build >> itself 4) pkg delete synth (system is once again clean) 5) pkg add -F >> /path/to/synth/packages/synth-* > >> Now you have a system containing s/w built by itself. On an modest >> system less than 4 years old, it might take 30 minutes at most. > > I believe you could cd $PORTSDIR/ports-mgmt/synth and > make package-recursive |& tee build-12amd64.log (or whatever you want to > name the log file; this example if for shell tcsh)? That installs build dependencies on the system. That would be no better than running portmaster the first time. If you run the process I suggested, you'll end up with a self-hosted machine with no extra stuff installed. > For a system with pkgng, is there any difference in package format > between "make install", portmaster and portupgrade? There shouldn't be, the ports framework is responsible for creating the package. > If your system already has portmaster, you could portmaster > ports-mgmt/synth |& tee synth-12amd64.log? > > And then switch from portmaster to synth for all further ports > builds/updates? sure. Although it will still be dirty from portmaster so at that point you would gather a "prime list" of packages, feed thoughs into synth to create a local repository, remove all packages from the system and re-install them with the "prime list" and the new local repository. > It would not be necessary to start with a clean system for FreeBSD, as > opposed to NetBSD, or am I mistaken here? No, you can start anytime but I do recommend the procedure above to ensure the system is in good shape and doesn't contain unnecessary package installations. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus