From: "Ludovic Courtès" <ludo@gnu.org>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix beyond 1.0: let’s have a roadmap!
Date: Mon, 01 Jul 2019 11:36:43 +0200 [thread overview]
Message-ID: <87blyet7tg.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfbZKXwzv=efWBe3u-9r3dCqv=G+xPAdYMZwhaqFeXNY7Q@mail.gmail.com> (David Thompson's message of "Thu, 27 Jun 2019 16:28:29 -0400")
Hi David,
"Thompson, David" <dthompson2@worcester.edu> skribis:
> * Extend 'guix environment' to cover use-cases that people currently
> use docker-compose for
Could you clarify a bit what that would mean?
> * Improve UX of 'guix environment' by using sane defaults and
> conventions such as reading from 'guix.scm' file in current directory
Yup! I haven’t forgotten about your proposal at:
https://lists.gnu.org/archive/html/guix-devel/2017-08/msg00300.html
> * Add a small-scale, general-purpose, "serverless" computing
> environment a la AWS Lambda using g-expressions + call-with-container
> + a web server
Is it something akin to ‘remote-eval’ and ‘container-eval’?
https://issues.guix.gnu.org/issue/36162
> * Improve portable application bundles so that only files needed at
> runtime (no headers, docs, etc.) are included somehow (not sure how to
> do this one)
I guess it boils down to making packages “smaller”, possibly using
multiple outputs and generally paying attention to what ‘guix size’
reports.
> * Allow system services to run unprivileged (perhaps via user
> namespaces) so that each user may have their own shepherd instance
> (would be useful for other features, too, such as the first item in
> this list)
Makes sense to me.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-07-01 9:36 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 16:05 Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 16:36 ` P
2019-06-27 21:12 ` Ludovic Courtès
2019-06-27 17:06 ` Vagrant Cascadian
2019-06-27 21:17 ` Ludovic Courtès
2019-06-27 18:53 ` Jakob L. Kreuze
2019-06-27 21:18 ` Ludovic Courtès
2019-06-27 19:02 ` Alex Griffin
2019-06-27 22:33 ` swedebugia
2019-06-28 6:11 ` Julien Lepiller
2019-06-28 16:13 ` John Soo
2019-07-01 9:14 ` Ludovic Courtès
2019-07-01 11:57 ` Pierre Neidhardt
2019-07-07 14:15 ` Ludovic Courtès
2019-06-30 13:48 ` Giovanni Biscuolo
2019-07-01 9:16 ` Ludovic Courtès
2019-07-05 7:55 ` Giovanni Biscuolo
2019-07-01 10:05 ` Ludovic Courtès
2019-07-01 13:12 ` Alex Griffin
2019-07-05 8:35 ` Guix UCI comparison (was Re: Guix beyond 1.0: let’s have a roadmap!) Giovanni Biscuolo
2019-07-07 14:09 ` Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 19:33 ` Svante Signell
2019-06-27 21:25 ` Ludovic Courtès
2019-06-27 20:28 ` Thompson, David
2019-07-01 9:36 ` Ludovic Courtès [this message]
2019-07-01 10:39 ` Hartmut Goebel
2019-07-01 9:37 ` Ludovic Courtès
2019-06-27 22:01 ` Pierre Neidhardt
2019-06-27 22:24 ` Julien Lepiller
2019-07-01 9:48 ` Ludovic Courtès
2019-06-28 16:54 ` znavko
2019-06-28 17:07 ` swedebugia
2019-06-28 17:17 ` znavko
2019-06-29 1:35 ` ison
2019-06-29 4:51 ` pelzflorian (Florian Pelz)
2019-07-01 9:51 ` Ludovic Courtès
2019-06-30 13:13 ` Giovanni Biscuolo
2019-06-30 13:38 ` Robert Vollmert
2019-07-01 9:55 ` Ludovic Courtès
2019-07-05 11:47 ` Robert Vollmert
2019-07-09 10:22 ` Ricardo Wurmus
2019-07-09 10:58 ` Robert Vollmert
[not found] ` <877e97vws8.fsf%40gnu.org504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net>
2019-07-26 7:00 ` Ben Sturmfels
2019-07-26 8:27 ` Pierre Neidhardt
2019-08-22 20:59 ` Ludovic Courtès
2019-06-30 13:28 ` Christopher Lemmer Webber
2019-07-01 9:57 ` Ludovic Courtès
2019-07-01 11:47 ` Pierre Neidhardt
2019-06-30 13:59 ` Giovanni Biscuolo
2019-07-01 9:58 ` Ludovic Courtès
2019-07-09 13:32 ` P
2019-07-11 10:11 ` Ricardo Wurmus
2019-07-11 15:17 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-06-28 18:57 Jesse Gibbons
2019-07-01 10:14 ` zimoun
2019-07-01 19:38 ` Jesse Gibbons
2019-07-06 12:50 matias_jose_seco
2019-07-07 14:20 ` Ludovic Courtès
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=87blyet7tg.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).