From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] guix environment: Add --ad-hoc option.
Date: Thu, 28 May 2015 23:53:12 +0200 [thread overview]
Message-ID: <871ti0tlmf.fsf@gnu.org> (raw)
In-Reply-To: <87d21kg98b.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Thu, 28 May 2015 08:47:00 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> I find myself frequently wanting to quickly create an environment with
> just a few packages in it, without having to go through the song and
> dance of creating a package expression for it. This patch addresses
> this use-case.
Yeah, nice!
> From 30a5b0f61e5c4a0e0244015f127ba3255f834139 Mon Sep 17 00:00:00 2001
> From: David Thompson <davet@gnu.org>
> Date: Thu, 28 May 2015 08:41:04 -0400
> Subject: [PATCH] guix environment: Add --ad-hoc option.
>
> * guix/scripts/environment.scm (%options): Add "ad-hoc" option.
> (show-help): Display help for "--ad-hoc".
> (packages+propagated-inputs): New procedure.
> (guix-environment): Create ad hoc environment when asked.
> * doc/guix.texi ("invoking guix environment"): Document it.
LGTM!
> +@item --ad-hoc
> +Include all specified packages in the resulting environment, as if an ad
> +hoc package were defined with them as inputs. This option is useful for
@i{ad hoc}
> +quickly creating an environment without having to write a package
> +expression to contain the desired inputs.
Maybe add an example, like:
For instance, the command:
@example
guix environment --ad-hoc guile guile-sdl -E guile
@end example
runs @command{guile} in an environment where Guile and Guile-SDL are
available.
OK with these changes.
Thank you!
Ludo’.
prev parent reply other threads:[~2015-05-28 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 12:47 [PATCH] guix environment: Add --ad-hoc option David Thompson
2015-05-28 21:53 ` Ludovic Courtès [this message]
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=871ti0tlmf.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.