From owner-freebsd-ports@freebsd.org Tue Jun 13 22:51:38 2017 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 09DE9C08690 for ; Tue, 13 Jun 2017 22:51:38 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.227]) (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 DC41B6F47C for ; Tue, 13 Jun 2017 22:51:37 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:60989] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id FF/F6-01815-17C60495; Tue, 13 Jun 2017 22:51:30 +0000 Date: Tue, 13 Jun 2017 22:51:33 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-ports@freebsd.org CC: Jonathan Chen Subject: Re: Synth: copying installation to second computer References: <53.C8.03935.FCF7F395@dnvrco-omsmta01> X-RR-Connecting-IP: 107.14.64.88: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: Tue, 13 Jun 2017 22:51:38 -0000 > On 13 June 2017 at 18:01, Thomas Mueller wrote: > > I just managed to install (first part) ports-mgmt/synth on FreeBSD 11.1-PRERELEASE amd64, using portmaster after deleting all packages except pkg and portmaster. Those old packages were no good anyway due to shared libraaries being out of sync. > > Now I want to convert packages to synth repository format and copy this installation to another computer with same FreeBSD 11.1-PRERELEASE using NFS, doing as little recompilation as possible. > > This is my first (partway) success after an attempt to build synth on FreeBSD-CURRENT amd64, before ino64, was stopped by a system crash and reboot while I was sleeping. > > I looked through README.md and man synth, but there are still some hazy points. Or is it easier than I think? > The thing to note is that ports-mgmt/synth is a repository builder. > Coming from portupgrade or portmaster, a user may think that it is > rebuilding too many packages for a simple port change, but what it is > doing is verifying that the chain of construction for each port is > working as expected. The first build is always going to be long, but > will do concurrent builds as much as it much as possible. > Once you have a complete repo on one of your machines, you can simply > serve up the /var/synth/live_packages using www/apache24 or even ssh. > On each of the remote hosts, all you have to do is to add a > /usr/local/etc/pkg/repos/my-local-repo.conf entry, eg: # > # Locally built packages # > localrepo: { > url : http://my-build-host/live_packages, > priority : 20, > enabled : yes, } > And then you're good to go with "pkg upgrade -r localrepo" on each of > the remote hosts. > Cheers. > Jonathan Chen I think my main concern is getting packages into a synth-recognized repository. I would use NFS rather than http. I would need to be sure to disable freebsd.org server in the conf, think I just did, now need to check on the other computer. I don't really want to have to rebuild synth and dependencies redundantly after all are installed on first build-host computer. But I would want to use synth on either computer without depending on the other computer; what I am concerned with now is getting started. Tom