From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Running IceCat in a container
Date: Thu, 25 Jan 2018 15:34:48 +0100 [thread overview]
Message-ID: <87efmeuhvb.fsf@gnu.org> (raw)
In-Reply-To: <87tvvlrzlc.fsf@gnu.org> (Mike Gerwitz's message of "Tue, 16 Jan 2018 21:25:19 -0500")
Mike Gerwitz <mtg@gnu.org> skribis:
> On Tue, Jan 16, 2018 at 17:30:42 +0100, Ludovic Courtès wrote:
[...]
>> But really, we should make a specific tool for this.
>>
>> Thoughts?
>
> Yes, though I'd be curious how you'd approach it---each package requires
> certain paths be shared, and those paths would further depend on user
> privacy preferences, so need to be able to be overridden.
For a start, we could simply share everything that’s in:
guix gc -R $(guix build the-package)
plus /tmp/.X11-unix, maybe $PWD, and a few more.
After that we could add the option to let users define what needs to be
shared (like the ‘file-system-mapping’ API we already have). We could
have a predefined settings for X11 and console apps to minimize
boilerplate. And like you write, the settings could be added as package
metadata.
Plash (Mark Seaborn’s POLA shell which used to live at
<http://plash.beasts.org/>) would automatically determine what needs to
be mapped based on the command line. For instance, if you typed:
gcc -o foo.o ~/src/bar/foo.c
then it would map ~/src/bar/foo.c as read-only and $(dirname foo.o) as
read-write.
Food for thought!
Ludo’.
next prev parent reply other threads:[~2018-01-25 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 1:56 Running IceCat in a container Mike Gerwitz
2018-01-16 16:30 ` Ludovic Courtès
2018-01-17 2:25 ` Mike Gerwitz
2018-01-17 19:05 ` Mike Gerwitz
2018-01-17 23:20 ` Leo Famulari
2018-01-18 1:53 ` Mike Gerwitz
2018-01-25 14:34 ` Ludovic Courtès [this message]
2018-01-25 22:16 ` Ludovic Courtès
2018-01-26 3:52 ` Mike Gerwitz
2018-01-29 16:47 ` Ludovic Courtès
2018-01-30 2:19 ` Ricardo Wurmus
2018-01-30 17:21 ` Running code from packs in containers Ludovic Courtès
2018-03-19 17:42 ` Running IceCat in a container ng0
2018-01-29 16:48 ` 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=87efmeuhvb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mtg@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.
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).