From: Shea Levy <shea@shealevy.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "gnu-system-discuss@gnu.org" <gnu-system-discuss@gnu.org>,
"guile-user@gnu.org" <guile-user@gnu.org>,
nix-dev <nix-dev@cs.uu.nl>
Subject: Re: [***SPAM***] [ANN] Guix, functional package management from Guile
Date: Sat, 7 Jul 2012 18:13:52 -0400 [thread overview]
Message-ID: <E9ED0B09-261A-4C6E-81E5-54D7797D6C20@shealevy.com> (raw)
In-Reply-To: <87bojrp76i.fsf@gnu.org>
Hi Ludo,
Very cool work, I'll have to check it out. One queston and one quick note:
On Jul 7, 2012, at 5:55 PM, ludo@gnu.org (Ludovic Courtès) wrote:
> in Guix, the cheat code is
> the ‘nixpkgs-derivation’ procedure. :-)
Does the referenced derivation need to actually be in nixpkgs? I assume this works by calling nix-instantiate?
>
> it supports multiple-derivation outputs (where a build
> produces several files under /nix/store)
Just FYI, multiple-outputs support is not complete at the nix-store level. In particular, if you have one output of a derivation realized but not all (because you gc'd the others or got the one via a substitutor), nix-store can't realize the non-realized ones directly yet. There may be other issues I'm not aware of too.
Cheers,
Shea
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
next prev parent reply other threads:[~2012-07-07 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 21:55 [ANN] Guix, functional package management from Guile Ludovic Courtès
2012-07-07 22:13 ` Shea Levy [this message]
2012-07-09 8:50 ` [***SPAM***] " Sander van der Burg - EWI
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E9ED0B09-261A-4C6E-81E5-54D7797D6C20@shealevy.com \
--to=shea@shealevy.com \
--cc=gnu-system-discuss@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=nix-dev@cs.uu.nl \
/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.
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).