unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Self-contained Guix tarball
Date: Thu, 16 Apr 2015 07:33:55 +0200	[thread overview]
Message-ID: <20150416053355.GD21015@thebird.nl> (raw)
In-Reply-To: <871tjlxen6.fsf@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? 

Pj.

On Wed, Apr 15, 2015 at 11:31:09PM +0200, Ludovic Courtès 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.
> 
> Ludo???.
> 
> 
> 2.1 Binary Installation
> =======================
> 
> 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.
> 
>    Installing goes along these lines:
> 
>   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 already
>      running the kernel Linux, and so on.
> 
>   2. As ???root???, run:
> 
>           # cd /
>           # tar xf guix-binary-0.8.2.SYSTEM.tar.xz
> 
>      This creates ???/gnu/store??? (*note The Store::), ???/var/guix???, and
>      ???/root/.guix-profile???.  ???/root/.guix-profile??? is a ready-to-use
>      profile for ???root??? where Guix is installed.
> 
>   3. Setup the daemon as explained below (*note Setting Up the
>      Daemon::), and run it:
> 
>           # /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder
> 
>   4. Make the ???guix??? command available to other users on the machine,
>      for instance with:
> 
>           # mkdir -p /usr/local/bin
>           # cd /usr/local/bin
>           # ln -s /root/.guix-profile/bin/guix
> 
>    And that???s it!
> 
>    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.
> 
>    The tarball in question can be (re)produced simply by running the
> following command in the Guix source tree:
> 
>      make guix-binary.SYSTEM.tar.xz
> 
>    ---------- Footnotes ----------
> 
>    (1) As usual, make sure to download the associated ???.sig??? file and to
> verify the authenticity of the tarball against it!
> 

-- 

  reply	other threads:[~2015-04-16  5:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  8:46 Copying whole /gnu/store from USB does not work Pjotr Prins
2015-04-10 11:48 ` Ludovic Courtès
2015-04-10 13:14   ` Pjotr Prins
2015-04-10 13:41     ` David Thompson
2015-04-12 10:28     ` Copying whole /gnu/store from USB does not work (SOLVED) Pjotr Prins
2015-04-12 12:29       ` Ludovic Courtès
2015-04-12 20:07     ` Self-contained Guix tarball Ludovic Courtès
2015-04-13  6:54       ` Pjotr Prins
2015-04-13  9:57         ` Ludovic Courtès
2015-04-13 10:05           ` Pjotr Prins
2015-04-13 13:29           ` Mark H Weaver
2015-04-14 21:33             ` Ludovic Courtès
2015-04-13 15:47       ` Thompson, David
2015-04-15 21:31       ` Ludovic Courtès
2015-04-16  5:33         ` Pjotr Prins [this message]
2015-04-18 21:23           ` Ludovic Courtès
2015-04-19  8:18             ` Pjotr Prins
2015-04-19 20:09               ` Ludovic Courtès
2015-04-19 13:34             ` Taylan Ulrich Bayırlı/Kammer
2015-04-20 20:49               ` Ludovic Courtès
2015-04-21  7:03                 ` Pjotr Prins
2015-04-21  7:19                   ` Pjotr Prins
2015-04-21  8:18                     ` Ludovic Courtès
2015-04-21  8:44                       ` Pjotr Prins
2015-04-21 12:16                         ` Ludovic Courtès
2015-04-21  8:11                   ` Ludovic Courtès
2015-04-21  8:37                     ` Pjotr Prins
2015-04-21 10:08                       ` Ricardo Wurmus
2015-04-21 10:17                         ` Pjotr Prins
2015-04-21 12:08                           ` Andreas Enge
2015-04-21 12:12                       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150416053355.GD21015@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).