unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Petter <petter@mykolab.ch>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Mention "guix pull" during installation.
Date: Sat, 17 Dec 2016 12:38:56 -0500	[thread overview]
Message-ID: <20161217173856.GA30440@jasmine> (raw)
In-Reply-To: <82b3233597949c866c26628054117ee3@mykolab.ch>

On Fri, Dec 16, 2016 at 09:38:02AM +0100, Petter wrote:
> good experience because of this. Proposing a patch to add this to the
> manual.

Thanks for looking out for the new user experience, which one tends to
forget as time passes :)

> * doc/guix.texi (Proceeding with the Installation): Add "guix pull".

> +At this point it is advisable to update the system, especially if the
> +installer is more than a few weeks old. Then most, if not all, packages
> +will be available as substitutes.
> +
> +@example
> +guix pull
> +@end example

So far, in practice, this seems to become necessary as a given release
grows old. This is a negative side effect of some limitations of our
build farm infrastructure.

Specifically, we start to garbage collect the substitutes that
correspond to a release as time goes by, for two reasons: we need the
disk space, and more importantly, our method of registering garbage
collector roots [0] is still rather crude.

Some of us are working on a different method of registering garbage
collector roots that will allow us to tell Hydra, "Keep the substitutes
for release X", or "Keep the substitutes for the master branch in the
last 3 months".

I've recently gave an explanation of why I think using `guix pull`
before installing GuixSD should not be recommended unconditionally:

http://lists.gnu.org/archive/html/bug-guix/2016-11/msg00047.html

In the specific case of installing GuixSD 0.11.0 today, `guix pull` is
necessary, because we lack the substitutes, and some packages can't be
built at all now [1]. But, adding these lines to the manual now won't
make it show up in the 0.11.0 installer manual.

I think we should work on improving our infrastructure in the next
release cycle, and revisit this change to the manual if we are still
having problems before the 0.13.0 release.

What does everyone think?

[0]
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-gc.html

[1] For example:
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=d404a6f9711c8dcc1cc6cf55d8c07901aa450192

  reply	other threads:[~2016-12-17 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  8:38 [PATCH] doc: Mention "guix pull" during installation Petter
2016-12-17 17:38 ` Leo Famulari [this message]
2016-12-18 11:00   ` Ludovic Courtès
2016-12-19  7:41     ` Alex Sassmannshausen
2016-12-18 12:05 ` Theodoros Foradis
2016-12-19  8:09   ` Ra
2016-12-19 10:52   ` 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=20161217173856.GA30440@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=petter@mykolab.ch \
    /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).