From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: Why don't we have "Guix channels"?
Date: Thu, 08 Dec 2016 23:29:39 -0800 [thread overview]
Message-ID: <87y3zptva4.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi,
Nix has a feature called "channels". To quote the docs, "a channel is a
Nix mechanism for distributing Nix expressions and associated binaries"
[1]. It sounds like this includes the nix tools like "nix-build", but
I'm not sure. In any case, it's clearly similar to "guix pull", but at
first blush channels seems more featureful and more useful. Here are
some features:
* A user can "subscribe" [2] to multiple channels ("stable", "unstable",
etc.).
* "Correctness: The channel is only updated to a new revision of
NixOS/Nixpkgs if it passes certain tests" [3].
* "Efficiency: The channel is only updated after all Hydra builds in
that revision have finished, *and* all binaries have been mirrored"
[3].
* "In principle, you can do rollbacks on the channels profile ("nix-env
-p /nix/var/nix/profiles/per-user/root/channels --rollback") if you
don't like the result of a 'nix-channel --update'" [3].
These all sound like features which would be nice to have in Guix, so I
wonder: why doesn't Guix have "channels", too?
For more information about Nix channels, see here (Eelco's thesis [4]
includes more technical details - search it for the word "channel"):
[1] https://nixos.org/nixos/manual/#sec-upgrading
[2] https://nixos.org/nix/manual/#sec-channels
[3] https://nixos.org/wiki/Install/remove_software#nix-channels
[4] http://nixos.org/%7Eeelco/pubs/phd-thesis.pdf
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2016-12-09 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 7:29 Chris Marusich [this message]
2016-12-09 7:35 ` Why don't we have "Guix channels"? Chris Marusich
2016-12-09 10:09 ` Pjotr Prins
2016-12-09 14:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3zptva4.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.