[bug#60112] [PATCH v2] website: Add post about guix shell fhs option.

[John Kehayias]

Hello,

On Wed, Jan 04, 2023 at 11:31 AM, Ludovic Courtès wrote:

> The Tor Browser example would be nice.  No other suggestions from me!
>

Added, with a slight tweak from the original mailing list message (and with 
credit given). The gcc:lib input is smaller than libgccjit and I believe the 
DISPLAY/XAUTHORITY sharing is more general (or at least works for me, the 
original related to GDM which I don't use).

>From your previous comments:

On Mon, Dec 26, 2022 at 12:58 AM, Ludovic Courtès wrote:

>> +++ b/website/posts/guix-shell-fhs.md
>> @@ -0,0 +1,140 @@
>> +title: FHS Comes to Guix Containers
>
> Should we spell “FHS” out?
>

I did now, which is more descriptive and I don't think too long. I didn't 
include the (FHS) abbreviation though (we could).

>> +GNU Guix is different from most other GNU/Linux distributions and perhaps 
>> nowhere is
>> that more obvious than the organization of the filesystem: Guix does not 
>> conform to the
>> [Filesystem Hierarchy 
>> Standard](<https://refspecs.linuxfoundation.org/fhs.shtml>) (FHS).
>> In practical terms, this means there is no global `/lib` containing 
>> libraries, `/bin`
>> containing binaries,<sup><a id="fnr.1" class="footref" href="#fn.1"
>> role="doc-backlink">1</a></sup> and so on. This is very much at the core of 
>> how Guix
>> works and some of the convenient features, like per-user installation of 
>> programs
>> (different versions, for instance) and a declarative system configuration 
>> where the
>> system is determined from a configuration file.
>
> Haunt uses Guile-Commonmark, and I don’t think we can use inline HTML
> nor footnotes actually.  A bit of a bummer, but maybe you can
> approximate that with:
>
>   `/bin` containing binaries¹, …
>
> and at the bottom:
>
>   ¹ Blah.
>

Ah. I did just that, no links to jump back and forth then. The second note I 
could just have as a parenthetical paragraph, but the first would be a bit 
cluttered. So I kept them both as notes, but I'm not attached to the style if 
we want to change it.

> It might be worth mentioning somewhere that the feature is included in
> the just-released 1.4.0 now.
>

Good idea, noted and linked to the release announcement post.

>> +Here is a very simple example:
>> +
>> +    $ guix shell --container --emulate-fhs coreutils -- ls /bin | head
>> +    [
>> +    b2sum
>> +    base32
>> +    base64
>> +    basename
>> +    basenc
>> +    cat
>> +    catchsegv
>> +    chcon
>> +    chgrp
>
> Example examples in triple backquotes (i.e., ```), without extra
> indentation.
>

Fixed (guess the org exporter defaulted to a different style). I didn't see any 
change in appearance with marking all of these as 'sh' examples, but added that 
in case it is useful at some point.

>> +[![img](guix-shell-fhs.gif "Or, if you like to see it more in motion, 
>> here's a
>> gif.")](guix-shell-fhs.gif)
>
> The syntax is:
>
>   ![Alt text.](/static/blog/img/…)
>
> Note that the alt text is not shown unless one disables pictures or
> hovers over the picture.  So “Or, if you like […]” should probably be
> written above the image.
>

Correct, that was supposed to be a caption or before the image. Fixed and added 
credit for the image.

> You can test the web site with:
>
>   guix shell
>
> and then:
>
>   export GUIX_WEB_SITE_LOCAL=y
>   haunt build
>   haunt serve
>

Thanks, that was handy.

Other than these fixes, adding the Tor Browser example, and some stylistic 
changes (added some links too), the content should be basically the same as the 
first version.

Happy to add/subtract anything and anything else if anyone has suggestions.

John

0001-website-Add-post-about-guix-shell-fhs-option.patch
Description: Text Data