From: John Kehayias <john.kehayias@protonmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>, help-guix@gnu.org
Subject: Re: Drafting a Guix blog post on the FHS container
Date: Fri, 16 Dec 2022 07:35:27 +0000 [thread overview]
Message-ID: <875yebls20.fsf@protonmail.com> (raw)
In-Reply-To: <87edt0oh0a.fsf@gnu.org>
Hi again!
On Thu, Dec 15, 2022 at 03:53 PM, Ludovic Courtès wrote:
> Hello!
>
> John Kehayias <john.kehayias@protonmail.com> skribis:
>
>> First, let's dive right into a big one: the popular VSCodium editor. This is a freely
>> licensed build of VS Code: <https://github.com/VSCodium/vscodium#why-does-this-exist>
>>
>> This comes in AppImage format. Downloading it and making it executable (with a 'chmod
>> +x') I can run it in a container as
>>
>> guix shell -CNF -D ungoogled-chromium gcc:lib \
>> --preserve='^DISPLAY$' --preserve='^XAUTHORITY$' --share=$XAUTHORITY \
>> --preserve='^DBUS_' --expose=/var/run/dbus \
>> --expose=/sys/dev --expose=/sys/devices --expose=/dev/dri \
>> -- ./VSCodium-1.74.0.22342.glibc2.17-x86_64.AppImage --appimage-extract-and-run
>
> The code in that AppImage is free software, right?
>
The usual disclaimer of IANAL, but I linked to the part of their readme which describes the project licensing. So it seems all free to me, similar maybe to ungoogled-chromium: all the source without the telemetry and non-free branding, etc. But please do check.
>> Another example is to get the latest nightly builds of Rust, via <https://rustup.rs/>
>
> That’s a nice one too!
>
>> Happy to try other examples and to hear feedback on these!
>
> I think these are two good examples, likely to correspond to the kind of
> thing people may want to try.
>
Great, thanks!
>>> Actually you can use or get inspiration from this animated GIF if you
>>> like:
>>>
>>> <https://web.fdn.fr/~lcourtes/tmp/guix-shell-fhs.gif>
>>>
>>
>> Either I forgot to save this or wasn't able to access it before, and can't access it
>> now.
>
> Yeah, the TLS setup on that machine is broken, so you’d have to “Accept
> the risk and continue”; I sent you a copy off-list.
>
Thank you. I included it but realize now I forgot to add credit, so I can do that later.
> If we release on Monday, it would be great to have it published…
> tomorrow (Friday). Otherwise next Friday maybe?
>
It has gotten crazy here this week, hence my slow response (and not using my new found commit powers yet!). I've just sent the draft post which is the previous version with changes you suggested and a slightly expanded version of the examples from my previous message.
<https://issues.guix.gnu.org/60112>
I did some manual tweaking to the markdown export but I think it should look okay. Wasn't sure about the footnotes or if that should just be in-text. Oh, and now realized may want it with a fill column rather than long lines. (It always wraps nicely on my Emacs setup so I forget.)
I should be able to make quick edits tomorrow (it is very late here now), but we don't need to rush if there are other changes or checks anyone wants to make. I can also record some screen grabs if that is helpful.
> Thanks!
>
> Ludo’.
Thanks for the input, wish I had some more time this past week to have gotten this done earlier.
John
next prev parent reply other threads:[~2022-12-16 7:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 2:32 Drafting a Guix blog post on the FHS container 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 [this message]
2022-12-09 17:56 ` zimoun
2022-12-12 5:49 ` John Kehayias
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 23:39 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
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=875yebls20.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@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 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.