From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: 30480@debbugs.gnu.org
Subject: [bug#30480] [PATCH] environment: Add --manifest option.
Date: Mon, 19 Feb 2018 22:21:37 +0100 [thread overview]
Message-ID: <87r2pgekv2.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfby6A7KzDUf+a__fg2thAtte+4nXq-5b4vyADmH7NqoVg@mail.gmail.com> (David Thompson's message of "Thu, 15 Feb 2018 21:12:58 -0500")
Hi David!
"Thompson, David" <dthompson2@worcester.edu> skribis:
> In my lurkings I've seen people wondering why `guix environment`
> doesn't work with manifests. The answer is simply: I never thought to
> add it. This patch fixes that. The implementation is kind of
> interesting and might seem a little silly to people that know how
> manifests work. In order to support manifests with minimal code and
> make --manifest compose with other options I simply decompile the
> manifest back into a list of package/output tuples. That means in the
> case of `guix environment --manifest=foo.scm` the manifest is created,
> decompiled, and a new manifest created from that. Seems redundant!
> The advantage is that since --manifest composes with all the other
> ways to specify packages we can do absolutely bonkers things like
> `guix environment guile --ad-hoc ruby --manifest=foo.scm
> --manifest=bar.scm --load=frob.scm --expression='(@ (gnu packages
> python) python)'`. More realistically you'd use it to throw in an
> extra package or two with --ad-hoc.
Indeed, that makes a lot of sense. I wondered about doing that for
‘guix pack’ as well, it turns out to be more shenanigans than we’d like.
> From 47e0cf3bef26791c72222175899790a46c49af45 Mon Sep 17 00:00:00 2001
> From: David Thompson <dthompson2@worcester.edu>
> Date: Thu, 15 Feb 2018 20:54:28 -0500
> Subject: [PATCH] environment: Add --manifest option.
>
> * guix/scripts/environment.scm (show-help, %options): Add -m/--manifest.
> (options/resolve-packages): Handle manifests.
> * doc/guix.texi (Invoking guix environment): Document it.
Could you add an example in tests/guix-environment.sh that uses a
manifest with the “guile-bootstrap” package for instance?
OK with this change! :-)
Thank you,
Ludo’.
next prev parent reply other threads:[~2018-02-19 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 2:12 [bug#30480] [PATCH] environment: Add --manifest option Thompson, David
2018-02-16 5:58 ` Jan Nieuwenhuizen
2018-02-19 21:21 ` Ludovic Courtès [this message]
2018-02-21 3:25 ` Thompson, David
2018-02-21 22:10 ` Ludovic Courtès
2018-02-22 3:17 ` Thompson, David
2018-02-22 6:47 ` bug#30480: " Leo Famulari
2018-02-22 9:15 ` [bug#30480] " Andreas Enge
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=87r2pgekv2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30480@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
/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).