From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: New x86 machine
Date: Sat, 30 Aug 2014 22:07:48 +0200 [thread overview]
Message-ID: <87ha0tagh7.fsf@gnu.org> (raw)
In-Reply-To: <87fvgeiu1g.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Fri, 29 Aug 2014 22:35:23 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> From what I can tell, there is no official release tarball of Hydra. I
> guess we'd have to settle for packaging a snapshot of the git repo?
Yes.
> When trying to build Hydra, I get the error "configure: error: nix-store
> is required". Do I need to have Nix installed, or is there a configure
> flag I can pass to use Guix?
Hydra requires Nix for its command-line interface and for its Perl
bindings. But it uses only the low-level stuff (essentially what the
(guix store) module provides), which is compatible between Nix and Guix.
>> For the brave hacker, there’s also this option:
>>
>> 2b. Write a Hydra replacement in Scheme, probably building upon
>> David’s neat guix-web.
>
> I wonder how difficult this would be. I haven't explored the full
> feature set of Hydra, but I bet we have all the building blocks that we
> need. It would be very interesting to explore this more.
I think we’d rather think in terms of the features we need. The
3-process architecture described at
<http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc/manual>
under “Getting Started” should be mostly appropriate, I think.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-08-30 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 22:31 New x86 machine Jason Self
2014-08-29 13:04 ` Ludovic Courtès
2014-08-30 2:35 ` David Thompson
2014-08-30 20:07 ` Ludovic Courtès [this message]
2014-08-30 20:01 ` Sergio Durigan Junior
2014-08-31 20:03 ` 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=87ha0tagh7.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 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.