From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: Guix mentioned in Journal of Open Source Software (JOSS)
Date: Tue, 14 Jun 2016 14:30:21 +0200 [thread overview]
Message-ID: <8760tceyw2.fsf@gnu.org> (raw)
In-Reply-To: <idjfusgxi6c.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Tue, 14 Jun 2016 10:56:27 +0200")
Howdy!
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
>
>> We published a paper on GeneNetwork which uses Guix for deployment:
>>
>> http://joss.theoj.org/papers/10.21105/joss.00025
>
> Congratulations on getting the paper accepted!
Indeed, well done!
>> (1) Roel has suggested we should script the binary installation. I think
>> that is a fine idea. That was hurdle one.
>>
>> (2) Hurdle two is fixating the package tree. I would really like a
>>
>> git pull --version HASH
>
> “guix” or “git”?
I think ‘guix’, but eventually it’ll be almost the same:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22629
I think the plan outlined in this bug report should address your
concerns, Pjotr, and I agree it’d be very useful.
>> (3) I also think the default GUIX key should just be available. Why make
>> guix authorize an extra step? When I install guix, I WANT it.
>
> What default key do you mean?
For substitutes.
Maybe the 7 steps described under “Binary Installation” should be
replaced by a shell script that would be added in the binary tarball?
Hopefully it would be below 20 lines and people could easily check what
it does.
That script could also add the hydra.gnu.org key to the ACL.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-06-14 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:47 Guix mentioned in Journal of Open Source Software (JOSS) Pjotr Prins
2016-06-14 8:35 ` Ricardo Wurmus
2016-06-14 8:50 ` Alex Kost
2016-06-14 8:56 ` Ricardo Wurmus
2016-06-14 12:30 ` Ludovic Courtès [this message]
2016-06-14 9:22 ` Andy Wingo
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=8760tceyw2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).