From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 69587@debbugs.gnu.org
Subject: [bug#69587] [PATCH] doc: Add “Source Tree Structure” section.
Date: Fri, 08 Mar 2024 23:06:57 +0100 [thread overview]
Message-ID: <877cic2xa6.fsf@gnu.org> (raw)
In-Reply-To: <878r2sa9hd.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Fri, 08 Mar 2024 19:01:34 +0100")
Hello!
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> This section seems to be a good idea in general, but the examples are an
> opinionated selection. I believe the list should be small. Listing
> individual modules directly in ~/src/guix/guix directory is not useful
> to newcomers or often self-explanatory. gnu/installer, gnu/system,
> gnu/build, gnu/machine is not useful to know.
Are you suggesting to remove the examples?
If that’s the case, we might as well not add the section or it would
become a bullet list with three items (guix/, gnu/, and tests/), no?
The selection is opinionated, indeed. My thought was that it was a way
to connect the dots among things presented in the manual and to provide
a “guided tour” pretty much like Josselin’s talk.
> po is better not talked about, otherwise people edit translations
> directly in po, when they should use Weblate.
Not sure; there’s a link to “Translating Guix” that explains what to do.
>> +@table @file
>> +@item guix
>> +This is the location of core Guix mechanisms. A few examples:
>
> What does core mean?
The examples were meant to illustrate what is meant by “core”. Do you
think some other adjective or a longer description would help?
> Perhaps (guix …) should be listed after (gnu …) and defined as the
> Guix mechanisms that do not belong in gnu? Not quite sure either.
The order I chose is (roughly) from lower-level to higher-level:
(guix store) -> (guix derivation) -> (guix packages) -> …
… -> (gnu packages) -> (gnu system) -> …
Does that make sense?
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2024-03-08 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 16:37 [bug#69587] [PATCH] doc: Add “Source Tree Structure” section Ludovic Courtès
2024-03-08 18:01 ` pelzflorian (Florian Pelz)
2024-03-08 22:06 ` Ludovic Courtès [this message]
2024-03-09 14:38 ` pelzflorian (Florian Pelz)
2024-03-11 17:05 ` Ludovic Courtès
2024-03-11 18:09 ` pelzflorian (Florian Pelz)
2024-03-13 21:45 ` Ludovic Courtès
2024-03-14 11:30 ` pelzflorian (Florian Pelz)
2024-03-19 14:16 ` Ludovic Courtès
2024-03-20 10:49 ` [bug#69587] [PATCH v2] " Ludovic Courtès
2024-03-20 17:05 ` pelzflorian (Florian Pelz)
2024-03-21 16:49 ` bug#69587: " Ludovic Courtès
2024-03-12 16:35 ` [bug#69587] [PATCH] " Giovanni Biscuolo
2024-03-12 18:41 ` pelzflorian (Florian Pelz)
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=877cic2xa6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=69587@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).