From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Malconnected machines & guix pull Date: Fri, 11 Mar 2016 14:39:00 +0100 Message-ID: References: <56E15AF6.5040806@zwets.com> <20160310170451.GB22669@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeNHd-0000im-SF for guix-devel@gnu.org; Fri, 11 Mar 2016 08:39:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aeNHZ-0003aT-OW for guix-devel@gnu.org; Fri, 11 Mar 2016 08:39:13 -0500 Received: from venus.bbbm.mdc-berlin.de ([141.80.25.30]:39023) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeNHZ-0003aK-Hh for guix-devel@gnu.org; Fri, 11 Mar 2016 08:39:09 -0500 In-Reply-To: <20160310170451.GB22669@thebird.nl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Pjotr Prins Cc: guix-devel@gnu.org Pjotr Prins writes: > On Thu, Mar 10, 2016 at 04:44:30PM +0100, Ricardo Wurmus wrote: >>=20 >> Marco van Zwetselaar writes: >>=20 >> > In fact, what I am really looking for is a --substitute-urls option = for=20 >> > 'guix pull', or a way to separate the pull and the subsequent build,= so=20 >> > that I can make it connect to a 'guix publish'-ing server. >>=20 >> Instead of =E2=80=9Cguix pull=E2=80=9D may I suggest using git instead= ? Especially, >> when you have multiple machines on which Guix should run, it may make >> sense to just clone the Guix git repository once from the Internet, >> clone it to the other machines via local network, and then update once >> in a while via =E2=80=9Cgit pull=E2=80=9D (not =E2=80=9Cguix pull=E2=80= =9D). >>=20 >> You can create a link =E2=80=9C~/.config/guix/latest=E2=80=9D pointing= to, say, >> =E2=80=9C~/dev/guix=E2=80=9D (if that=E2=80=99s the directory holding = the cloned repository). >>=20 >> When you update with =E2=80=9Cgit pull=E2=80=9D you=E2=80=99ll only ha= ve to download recent >> changes, not the whole Guix code. >>=20 >> Does this make sense? >>=20 >> ~~ Ricardo > > This has the additional benefit of 'fixating' the dependencies and > having some control over status of packages. This is why we have a > gn-stable checkout of guix which is shared among deployments. And it > can save a lot of downloads.=20 Yeah, this achieves what in traditional package management scenarios is done by a repository mirror. In combination with local build hosts you can ensure that all packages at the current checkout are available as binary substitutes. ~~ Ricardo