From: ludo@gnu.org (Ludovic Courtès)
To: bug-guix@gnu.org
Subject: New “guix pull” command
Date: Wed, 20 Feb 2013 23:58:12 +0100 [thread overview]
Message-ID: <87r4kak2yj.fsf@gnu.org> (raw)
Hi,
Commit f651b47 adds a “guix pull” command. It fetches a Guix source
tarball, unpacks it, compiles Scheme code (so not the daemon), and
changes ~/.config/guix/latest to point to it.
The commit also changes the ‘guix’ command to put ~/.config/guix/latest
at the front of the search path (except when using ./pre-inst-env.)
This way, it allows users to at the same time update package
descriptions (like “apt-get update”) and the package manager itself.
I considered other options, such as making a package for Guix and
letting users install it in their profile. That would have provided
roll-back and everything for free. However, I came to the conclusion
that package management of the package manager itself deserves special
treatment, and should not be in the way of users.
The implementation has two main problems: it does not authenticate the
tarball it downloads, and downloads a full tarball (~5 MiB) every time.
We need a bit of infrastructure to fix that. We could have a process on
hydra.gnu.org that automatically signs tarballs with a pre-defined key.
For the second issue, there are Git, rsync, bsdiff, or even GNUnet that
could help, but that requires more thought.
Comments welcome!
Thanks,
Ludo’.
next reply other threads:[~2013-02-20 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 22:58 Ludovic Courtès [this message]
2013-02-21 19:34 ` New “guix pull” command Andreas Enge
2013-02-22 14:34 ` Ludovic Courtès
2013-02-22 16:59 ` Andreas Enge
2013-02-22 20:28 ` Ludovic Courtès
2013-02-22 20:44 ` Andreas Enge
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=87r4kak2yj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@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).