From: "Thompson, David" <dthompson2@worcester.edu>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The future of 'guix environment'
Date: Fri, 1 Sep 2017 09:13:13 -0400 [thread overview]
Message-ID: <CAJ=RwfbgdCM+RT-h1eZT29-ZOpn0m-qp2zSSM-2SUj5k4HNRVw@mail.gmail.com> (raw)
In-Reply-To: <87y3py63j4.fsf@gnu.org>
On Fri, Sep 1, 2017 at 7:50 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
> One thing I didn't see in your proposal is something like
>
> guix environment --manifest manifest.scm
>
> It really bothers me that I can only declaritavely populate/maintain
> named profiles. Do you have an idea about that?
Never thought about it before. Maybe --load could support evaluating
to a package, a manifest, or an environment? Seems like that might be
getting into crazy territory, but maybe not.
- Dave
next prev parent reply other threads:[~2017-09-01 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 13:22 The future of 'guix environment' Thompson, David
2017-08-30 15:11 ` 宋文武
2017-08-30 15:33 ` Leo Famulari
2017-08-30 15:43 ` Ricardo Wurmus
2017-08-31 15:00 ` Ludovic Courtès
2017-08-30 15:56 ` Andreas Enge
2017-08-31 1:28 ` Thompson, David
2017-09-01 3:57 ` Christopher Allan Webber
2017-09-01 13:15 ` Thompson, David
2017-09-02 21:06 ` Ludovic Courtès
2017-09-03 7:15 ` Jan Nieuwenhuizen
2017-09-05 12:42 ` Thompson, David
2017-09-05 14:34 ` Ludovic Courtès
2017-08-30 15:52 ` Andreas Enge
2017-08-31 7:18 ` Jan Nieuwenhuizen
2017-08-31 13:28 ` Thompson, David
2017-09-01 11:50 ` Jan Nieuwenhuizen
2017-09-01 12:08 ` Ricardo Wurmus
2017-09-01 12:25 ` Jan Nieuwenhuizen
2017-09-01 13:13 ` Thompson, David [this message]
2017-08-31 15:16 ` Ludovic Courtès
2017-09-01 0:29 ` Thompson, David
2017-09-02 21:09 ` Ludovic Courtès
2017-09-01 3:52 ` Christopher Allan Webber
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='CAJ=RwfbgdCM+RT-h1eZT29-ZOpn0m-qp2zSSM-2SUj5k4HNRVw@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=janneke@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).