From: Jookia <166291@gmail.com>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: thesis: guixsd should provide /usr/bin/env
Date: Tue, 1 Mar 2016 19:11:51 +1100 [thread overview]
Message-ID: <20160301081151.GA32120@novena-choice-citizen.lan> (raw)
In-Reply-To: <87si0aei0m.fsf@igalia.com>
On Tue, Mar 01, 2016 at 09:09:45AM +0100, Andy Wingo wrote:
> Hi :)
>
> > Ludovic Courtès writes:
> >
> >> Should we add a --fhs or --/usr/bin/env option to simplify this?
>
> I think /usr/bin/env is probably going to be insufficient -- lazy people
> like me are always going to be asking for more things :) If we can
> manage to expose a profile at /usr, that would be better, I think.
>
> On Mon 29 Feb 2016 19:11, Christopher Allan Webber <cwebber@dustycloud.org> writes:
>
> > Would this possibly screw us up on Hurd, where container support I don't
> > think exists?
>
> In general, I think we can have the Hurd inform but not gate Guix
> features.
>
> In this case, exposing a custom view of the file system to a sub-process
> is something that the Hurd should be able to do anyway :)
We can somewhat do this with containers already, perhaps it'd be best to have
hacks that run in containers?
> Andy
next prev parent reply other threads:[~2016-03-01 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 9:19 thesis: guixsd should provide /usr/bin/env Andy Wingo
2015-11-17 6:48 ` Ricardo Wurmus
2015-11-19 16:07 ` Ludovic Courtès
2015-11-19 17:35 ` Andy Wingo
2015-11-20 14:00 ` Ludovic Courtès
2015-11-20 15:58 ` Andy Wingo
2016-02-17 7:31 ` 宋文武
2016-02-17 7:52 ` Jookia
2016-02-29 9:41 ` Ludovic Courtès
2016-02-29 9:46 ` Ludovic Courtès
2016-02-29 18:11 ` Christopher Allan Webber
2016-03-01 8:09 ` Andy Wingo
2016-03-01 8:11 ` Jookia [this message]
2016-03-03 17:00 ` 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=20160301081151.GA32120@novena-choice-citizen.lan \
--to=166291@gmail.com \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.com \
/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).