From: David Thompson <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Improving the usability of 'guix environment'
Date: Tue, 10 Feb 2015 12:53:50 -0500 [thread overview]
Message-ID: <87a90lhcup.fsf@fsf.org> (raw)
In-Reply-To: <87lhk51xxa.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> David Thompson <dthompson2@worcester.edu> skribis:
>
>> But all of that boilerplate is unnecessary since it's not possible to
>> actually build the package successfully without a proper hash of the
>> source AFAICT. Really, I would rather just use a simple list of
>> packages:
>>
>> (list autoconf automake guile-2.0 guile-json libgcrypt)
>
> What about adding a case for the handling of ‘-l’ such that, if the file
> evaluates to a list of packages, it does what you suggest?
I'm hesitant to do that, because I would also like for a list of
packages to be usable for building the environment as it's done
currently. Only allowing a single package in a file is a limitation
right now.
>> I propose adding a new flag that indicates whether we want the packages
>> themselves or their inputs in the environment. If we assume that the
>> default behavior is to include the packages themselves, a --inputs flag
>> could indicate to use the package(s) inputs instead:
>>
>> guix environment --inputs emacs
>
> That makes sense.
>
> In terms of UI, what about rather something keeping an interface close
> to that of ‘guix package’:
>
> guix environment -i guile guile-sdl
> # semantically equivalent to ‘guix package -i guile guile-sdl’
So without the -i switch, it would behave as it does now? Okay, but I
guess I would prefer to optimize for the common case, which in my case
would be having -i on by default.
> Now that I think of it, we could even move -E to ‘guix package’ itself:
> that would make it easy to create a scratch environment based on an
> existing profile.
I'm a bit confused about that. Are you suggesting we merge 'guix
environment' into 'guix package'?
--
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate
next prev parent reply other threads:[~2015-02-10 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:45 Improving the usability of 'guix environment' David Thompson
2015-02-10 17:25 ` Ludovic Courtès
2015-02-10 17:53 ` David Thompson [this message]
2015-02-10 21:23 ` Ludovic Courtès
2015-02-13 13:47 ` David Thompson
2015-02-10 18:17 ` Andreas Enge
2015-02-10 18:35 ` David Thompson
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=87a90lhcup.fsf@fsf.org \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=ludo@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).