From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: Self-contained Guix tarball Date: Thu, 16 Apr 2015 07:33:55 +0200 Message-ID: <20150416053355.GD21015@thebird.nl> References: <20150410084651.GA23353@thebird.nl> <873848p5kd.fsf@gnu.org> <20150410131420.GB24509@thebird.nl> <87a8ydt8k8.fsf_-_@gnu.org> <871tjlxen6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35620) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YicRs-0000IZ-Vw for guix-devel@gnu.org; Thu, 16 Apr 2015 01:34:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YicRp-0000p7-QX for guix-devel@gnu.org; Thu, 16 Apr 2015 01:34:48 -0400 Content-Disposition: inline In-Reply-To: <871tjlxen6.fsf@gnu.org> 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: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org Great :). I would make it a little clearer that this is 'bootstrapping' and hype it a little more that now there is no reason NOT to install Guix. Only 100Mb on your HDD. The warning about overwriting a Guix installation should be earlier. Maybe point out that if you want to move a package with dependencies see another part of the documentation. BTW when Nix decided to go for a meta-database they lost something. I know it has good reasons (performance mostly) but it took away the self-containedness of packages. It would be nice just to be able to copy/del packages and rebuild the meta information. Do we have something like that?=20 Pj. On Wed, Apr 15, 2015 at 11:31:09PM +0200, Ludovic Court=E8s wrote: > I???ve documented installation from the binary tarball (which I plan to > distribute for the next release) in commit 09722b1. Please let me know > what you think. >=20 > Ludo???. >=20 >=20 > 2.1 Binary Installation > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > This section describes how to install Guix on an arbitrary system from = a > self-contained tarball providing binaries for Guix and for all its > dependencies. This is often quicker than installing from source, which > is described in the next sections. The only requirement is to have > GNU tar and Xz. >=20 > Installing goes along these lines: >=20 > 1. Download the binary tarball from > ???ftp://alpha.gnu.org/gnu/guix/guix-binary-0.8.2.SYSTEM.tar.xz???= (1), > where SYSTEM is ???x86_64-linux??? for an ???x86_64??? machine alr= eady > running the kernel Linux, and so on. >=20 > 2. As ???root???, run: >=20 > # cd / > # tar xf guix-binary-0.8.2.SYSTEM.tar.xz >=20 > This creates ???/gnu/store??? (*note The Store::), ???/var/guix???= , and > ???/root/.guix-profile???. ???/root/.guix-profile??? is a ready-t= o-use > profile for ???root??? where Guix is installed. >=20 > 3. Setup the daemon as explained below (*note Setting Up the > Daemon::), and run it: >=20 > # /root/.guix-profile/bin/guix-daemon --build-users-group=3Dg= uix-builder >=20 > 4. Make the ???guix??? command available to other users on the machin= e, > for instance with: >=20 > # mkdir -p /usr/local/bin > # cd /usr/local/bin > # ln -s /root/.guix-profile/bin/guix >=20 > And that???s it! >=20 > There are two things to note. First, don???t unpack the tarball on = a > working Guix system since that would overwrite its own essential files. > Second, the ???guix??? package must remain available in ???root??????s = profile, or > it would become subject to garbage collection???in which case you would > find yourself badly handicapped by the lack of the ???guix??? command. >=20 > The tarball in question can be (re)produced simply by running the > following command in the Guix source tree: >=20 > make guix-binary.SYSTEM.tar.xz >=20 > ---------- Footnotes ---------- >=20 > (1) As usual, make sure to download the associated ???.sig??? file a= nd to > verify the authenticity of the tarball against it! >=20 --=20