From owner-freebsd-ports@freebsd.org Sun Dec 18 09:43:46 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 EBEFFC857B6 for ; Sun, 18 Dec 2016 09:43:46 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CC8CC1EE2 for ; Sun, 18 Dec 2016 09:43:46 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:44826] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 2A/9A-31287-B4A56585; Sun, 18 Dec 2016 09:43:39 +0000 Date: Sun, 18 Dec 2016 09:43:31 +0000 Message-ID: <2A.9A.31287.B4A56585@dnvrco-omsmta01> From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues References: X-RR-Connecting-IP: 107.14.64.6:25 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: Sun, 18 Dec 2016 09:43:47 -0000 >From John Marino and my previous post: > > 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. I ran make all-depends-list from $PORTSDIR/ports-mgmt/synth. Dependencies looked like packages I would need anyway. I want to try to cross-compile Haiku and Linux toolchains (among other things). I looked for synth in the online wiki.freebsd.org, found nothing, but did find portupgrade (no portmaster). If FreeBSD users are to use synth, it needs to be in the documentation. Otherwise FreeBSD users will assume portupgrade or portmaster is the proper way to upgrade ports. I would have thought there would be an Ada for ther platforms like PowerPC and (Ultra)Sparc. Tom