From: John Kehayias <john.kehayias@protonmail.com>
To: Jim Newsome <jim@sporksmith.net>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: Drafting a Guix blog post on the FHS container
Date: Wed, 04 Jan 2023 18:16:01 +0000 [thread overview]
Message-ID: <87edsajhd0.fsf@protonmail.com> (raw)
In-Reply-To: <ed277b25-f3d5-4336-8d17-6d0d0cfa649d@app.fastmail.com>
Hi Jim,
On Wed, Jan 04, 2023 at 06:07 PM, Jim Newsome wrote:
> Thanks, looks good, and the command in your patch also works for me.
>
Great, thanks for testing!
> I agree that passing and exposing XAUTHORITY seems better. Experimentally, sharing the directory
> read-only also works (using `--expose` instead of `--share`) also works, but I'm not familiar enough with
> this mechanism to be confident that'll work for everyone, or whether making it read-only is worth the
> fuss.
>
Ah, you are right, that seems to be just fine for VSCodium and Tor, in my quick test. I think I'll change that.
> Btw it turns out that `libevent` and `openssl@1` can be dropped; they're already bundled. All together,
> here's my current "best" version:
>
> ```
> guix shell --container --network --emulate-fhs \
> --preserve='^DISPLAY$' --preserve='^XAUTHORITY$' --expose=$XAUTHORITY \
> alsa-lib bash coreutils dbus-glib file gcc:lib grep gtk+ \
> libcxx pciutils sed \
> -- ./start-tor-browser.desktop -v
> ```
Nice, thanks for that too! I tried eliminating a few random inputs, but they were needed. It is difficult sometimes to get a really minimal set, but this looks good to me.
John
next prev parent reply other threads:[~2023-01-04 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 23:39 Drafting a Guix blog post on the FHS container Jim Newsome
2022-12-19 21:28 ` Ludovic Courtès
2022-12-23 2:04 ` Csepp
2022-12-26 5:36 ` John Kehayias
2023-01-04 17:47 ` John Kehayias
2023-01-04 18:07 ` Jim Newsome
2023-01-04 18:16 ` John Kehayias [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 2:32 John Kehayias
2022-12-05 6:51 ` Wojtek Kosior via
2022-12-12 5:46 ` John Kehayias
2022-12-06 10:41 ` Ludovic Courtès
2022-12-12 6:33 ` John Kehayias
2022-12-15 14:53 ` Ludovic Courtès
2022-12-16 7:35 ` John Kehayias
2022-12-09 17:56 ` zimoun
2022-12-12 5:49 ` John Kehayias
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=87edsajhd0.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=jim@sporksmith.net \
/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).