From: Ricardo Wurmus <rekado@elephly.net>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The future of 'guix environment'
Date: Wed, 30 Aug 2017 17:43:57 +0200 [thread overview]
Message-ID: <87lgm1f4ci.fsf@elephly.net> (raw)
In-Reply-To: <87ziahytsq.fsf@member.fsf.org>
宋文武 <iyzsong@member.fsf.org> writes:
>> 5) Add support for Shepherd services. When an environment is created,
>> a new Shepherd process is launched to handle all the necessary
>> services. For a web application this could be nginx, mysql, redis,
>> etc. This feature can be implemented later, even post 1.0, provided
>> we agree upon using a <guix-environment> record type.
>
> Yes, maybe launch the services with a subcommand like 'guix environment
> up', so the shell entering 'guix environment' command can be run
> multiple times.
AFAIU the proposal, that’s precisely what we don’t want. Dave wants
users/developers to be able to specify the behaviour of the environment,
not just the packages that ought to be available. I’d expect all
services to be killed upon leaving the environment, so we don’t need to
have a separate command for bringing them up.
It is not clear to me if it should be possible to “attach” to an
environment that is “active” in another shell session (like it is
possible with Docker containers).
@Dave: I pretty much agree with all of the proposed changes. One thing
that may be lost, though, when using a new <guix-environment> record is
easy ad-hoc packaging.
Now I can use a guix.scm file both for building a Guix package and a
Docker image; I would expect that it would no longer be possible to
build a Guix package out of an environment file. On the other hand,
building a more fully featured container image would be even simpler
with this change.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-30 15:44 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgm1f4ci.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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.