From: Pjotr Prins <pjotr.public12@thebird.nl>
To: guix-devel@gnu.org
Subject: Re: Building Guix
Date: Fri, 9 May 2014 20:51:29 +0200 [thread overview]
Message-ID: <20140509185129.GB19961@thebird.nl> (raw)
In-Reply-To: <20140509105718.GA18552@thebird.nl>
On Fri, May 09, 2014 at 12:57:18PM +0200, Pjotr Prins wrote:
> Interestingly I found a Guix expression in Nixpkgs! It is dated, guix-0.3, but works. Anything I need to know to update that to guix-0.6? I may do just that :)
>
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/package-management/guix/default.nix
Two questions:
1. Why is guile not simply a build dependency? Or is is that the tar
ball is expected in place for bootstrapping and will fail otherwise.
Looks a bit odd to have guile in multiple places.
2. What do we do with the store? I know Nix should move to /gnu ;) My
personal solution would be to hard link between /nix and /gnu. Will
the default be good enough?
It will be a good thing to maintain this Nix package until Guix comes
with all the binary installation options that Nix has. Be interesting
to see when Debian accepts a Guix package. Don't see why not, really,
since they allow for rubygems, cpan etc.
Pj.
next prev parent reply other threads:[~2014-05-09 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 10:57 Building Guix Pjotr Prins
2014-05-09 12:33 ` Ludovic Courtès
2014-05-09 18:51 ` Pjotr Prins [this message]
2014-05-09 20:22 ` Ludovic Courtès
2014-05-10 6:46 ` Pjotr Prins
2014-05-10 13:06 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 12:32 Building GUIX Pjotr Prins
2014-05-08 12:52 ` Andreas Enge
2014-05-08 13:02 ` Pjotr Prins
2014-05-08 13:30 ` Pjotr Prins
2014-05-08 13:42 ` Cyril Roelandt
2014-05-08 14:56 ` Pjotr Prins
2014-05-08 15:08 ` Pjotr Prins
2014-05-08 19:53 ` Pjotr Prins
2014-05-08 21:08 ` Ludovic Courtès
2014-05-08 16:42 ` 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=20140509185129.GB19961@thebird.nl \
--to=pjotr.public12@thebird.nl \
--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.