From: ludo@gnu.org (Ludovic Courtès)
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: guix-devel@gnu.org
Subject: Re: Heads-up: New dependency on Guile-Gcrypt
Date: Wed, 12 Sep 2018 19:14:40 +0200 [thread overview]
Message-ID: <87k1nq7i4f.fsf@gnu.org> (raw)
In-Reply-To: <1536659695.3288.20.camel@tourbillion-technology.com> (Paul Garlick's message of "Tue, 11 Sep 2018 10:54:55 +0100")
Hello,
Paul Garlick <pgarlick@tourbillion-technology.com> skribis:
> I have just needed to introduce a couple of concepts in order to use
> the ./pre-inst-env commands in the git checkout. Firstly, I use a
> development environment created by:
Once you have run ‘guix pull’, the ‘guile-gcrypt’ package is known and
it’s an input to the ‘guix’ package. Thus, from there on, simply
running:
guix environment guix
should give you an environment that contains guile-gcrypt, guile-json,
guile, and the whole shebang. In that environment you should be able to
hack on Guix itself.
Does that make sense?
In anyway, if you found a way out, that’s good. :-)
Ludo’.
next prev parent reply other threads:[~2018-09-12 17:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 11:19 Heads-up: New dependency on Guile-Gcrypt Paul Garlick
2018-09-05 20:58 ` Ludovic Courtès
2018-09-06 9:24 ` Paul Garlick
2018-09-06 10:06 ` Ludovic Courtès
2018-09-06 11:58 ` Paul Garlick
2018-09-06 21:08 ` Ludovic Courtès
2018-09-10 9:34 ` Pjotr Prins
2018-09-10 11:15 ` Paul Garlick
2018-09-10 20:45 ` Ludovic Courtès
2018-09-11 9:54 ` Paul Garlick
2018-09-12 17:14 ` Ludovic Courtès [this message]
2018-09-14 19:17 ` Thorsten Wilms
2018-09-27 7:45 ` Ricardo Wurmus
2018-09-27 11:36 ` Thorsten Wilms
2018-09-06 21:14 ` Paul Garlick
-- strict thread matches above, loose matches on Subject: below --
2018-09-02 16:35 Ludovic Courtès
2018-09-03 10:36 ` Christopher Lemmer Webber
2018-09-04 20:07 ` Alex Vong
2018-09-04 20:14 ` Leo Famulari
2018-09-04 21:33 ` Ludovic Courtès
2018-09-05 23:24 ` Alex Vong
2018-09-06 9:21 ` 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
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=87k1nq7i4f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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).