From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Add "guix update" command
Date: Sat, 23 Jan 2016 22:35:20 +0100 [thread overview]
Message-ID: <87k2n0rnc7.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfbcyr=LNPaVp0mQKmpemRUk4OSUA3JDYVuWkAQJTf4ugQ@mail.gmail.com> (David Thompson's message of "Sat, 23 Jan 2016 14:37:46 -0500")
Hi!
I very much agree with what David wrote.
Note that NixOS has been merged into Nixpkgs several months ago
precisely for the reasons David gave.
That Nix remains separate from Nixpkgs/NixOS can be problematic because
as new features of Nix language get used in Nixpkgs,
backward-compatibility is broken (and adding features to the language is
not uncommon since Nix is an external DSL that becomes less and less DS,
as is often the case with DSLs ;-)).
Ludo’.
next prev parent reply other threads:[~2016-01-23 21:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 10:02 [PATCH 0/1] Provide icons for transmission-gtk Leo Famulari
2016-01-20 10:02 ` [PATCH 1/1] gnu: transmission-gtk: Add icon dependencies Leo Famulari
2016-01-22 17:15 ` Ludovic Courtès
2016-01-22 19:27 ` Leo Famulari
2016-01-23 16:36 ` Ludovic Courtès
2016-01-23 18:11 ` Add "guix update" command Fabian Harfert
2016-01-23 18:28 ` Friedrich Herbst
2016-01-23 19:37 ` Thompson, David
2016-01-23 21:35 ` Ludovic Courtès [this message]
2016-01-28 4:44 ` [PATCH 1/1] gnu: transmission-gtk: Add icon dependencies Leo Famulari
2016-01-31 9:38 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-01-23 18:20 Add "guix update" command Fabian Harfert
2016-01-23 19:27 ` Christopher Allan Webber
2015-09-16 15:45 [PATCH] Add cufflinks Ricardo Wurmus
2015-09-16 17:10 ` Ludovic Courtès
2015-09-16 19:56 ` Andreas Enge
2015-09-16 20:06 ` Ludovic Courtès
2015-09-16 20:07 ` Ricardo Wurmus
2016-01-23 8:14 ` Ricardo Wurmus
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=87k2n0rnc7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--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 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).