From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 69587@debbugs.gnu.org
Subject: [bug#69587] [PATCH] doc: Add “Source Tree Structure” section.
Date: Tue, 12 Mar 2024 19:41:06 +0100 [thread overview]
Message-ID: <87edcfthrx.fsf@pelzflorian.de> (raw)
In-Reply-To: <877ci7tnki.fsf@xelera.eu> (Giovanni Biscuolo's message of "Tue, 12 Mar 2024 17:35:57 +0100")
Thank you Giovanni for voicing support; I’m afraid I sounded more
opposed than I am.
Giovanni Biscuolo <g@xelera.eu> writes:
> Also, please don't (dis)miss the usefulness of such documentation as a
> sort of meta-literate programming, probably also useful for expert Guix
> programmers too, IMHO
Do you think the following controversial parts should stay? But what is
their audience, and why explain them but not the directories build-aux
and nix and some other not so important files in guix?
‘gnu/system’
These are core Guix System modules, such as:
‘(gnu system)’
Defines ‘operating-system’ (*note operating-system
Reference::).
‘(gnu system file-systems)’
Defines ‘file-system’ (*note File Systems::).
‘(gnu system mapped-devices)’
Defines ‘mapped-device’ (*note Mapped Devices::).
‘gnu/build’
These are modules that are either used on the “build side” when
building operating systems or packages, or at run time by operating
systems.
‘(gnu build accounts)’
Creating ‘/etc/passwd’, ‘/etc/shadow’, etc. (*note User
Accounts::).
‘(gnu build activation)’
Activating an operating system at boot time or reconfiguration
time.
‘(gnu build file-systems)’
Searching, checking, and mounting file systems.
‘(gnu build linux-boot)’
‘(gnu build hurd-boot)’
Booting GNU/Linux and GNU/Hurd operating systems.
‘(gnu build linux-initrd)’
Creating a Linux initial RAM disk (*note Initial RAM Disk::).
[…]
‘gnu/installer’
This contains the text-mode graphical system installer (*note
Guided Graphical Installation::).
‘gnu/machine’
These are the “machine abstractions” used by ‘guix deploy’ (*note
Invoking guix deploy::).
[…]
‘po’
This is the location of translations of Guix itself, of package
synopses and descriptions, of the manual, and of the cookbook
(*note Translating Guix::).
> Last but not least, I have a feeling it's time to split the Guix manual
> in two: one for users, like "GNU Guix User Manual" and one for
> programmers [1], like "GNU Guix Programmer Manual", with chapters like
> "Programming Interface", "Platforms", "Bootstrapping", "Porting",
> "Contributing"... but that's another story, OT here.
Hmm why? But yes, another story.
Regards,
Florian
prev parent reply other threads:[~2024-03-12 18:42 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
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) [this message]
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=87edcfthrx.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=69587@debbugs.gnu.org \
--cc=g@xelera.eu \
--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.