From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] environment: Add --inclusive option.
Date: Fri, 20 Mar 2015 20:20:14 +0100 [thread overview]
Message-ID: <87vbhv8oi9.fsf@gnu.org> (raw)
In-Reply-To: <87lhitzvzx.fsf@fsf.org> (David Thompson's message of "Wed, 18 Mar 2015 20:11:46 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> From 3d97dbcf1907a67ed25fd90c09eb88d1b136d31a Mon Sep 17 00:00:00 2001
> From: David Thompson <dthompson2@worcester.edu>
> Date: Wed, 18 Mar 2015 20:01:12 -0400
> Subject: [PATCH 2/2] environment: Add --inclusive option.
>
> * guix/scripts/environment.scm (show-help): Add help.
> (%default-options): Add 'inclusive?'.
> (%options): Add 'inclusive' option.
> (packages->transitive-inputs): Add 'inclusive?' argument.
> (guix-environment): Use 'inclusive' option.
It’s a good idea.
Though I guess in the SDL example and similar use cases, it’s often
enough to make an environment that contains PACKAGES as their propagated
inputs (recursively), but not their inputs.
> +@item --inclusive
> +@item -i
> +Include @var{packages}@dots{} in the new environment in addition to
> +their inputs. Useful for creating an environment from arbitrary
^^
“This is useful for”
> + -i, --inclusive include PACKAGE... in new environment"))
“in the new environment”
OK to push with these changes, thank you!
Ludo’.
prev parent reply other threads:[~2015-03-20 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 0:08 [PATCH 0/2] environment: Add --inclusive option David Thompson
2015-03-19 0:11 ` [PATCH 1/2] packages: Expose transitive-inputs David Thompson
2015-03-19 10:34 ` David Thompson
2015-03-19 0:11 ` [PATCH 2/2] environment: Add --inclusive option David Thompson
2015-03-20 0:55 ` David Thompson
2015-03-20 19:20 ` 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
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=87vbhv8oi9.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 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).