From: Simon Tournier <zimon.toutoune@gmail.com>
To: rms@gnu.org
Cc: jb@jeremybryant.net, guix-devel@gnu.org, bjorn.bidar@thaodan.de,
arne_bab@web.de, suhailsingh247@gmail.com
Subject: Re: GNU Manuals in Info/HTML format via Guix?
Date: Thu, 09 Jan 2025 12:32:09 +0100 [thread overview]
Message-ID: <878qrk5ikm.fsf@gmail.com> (raw)
In-Reply-To: <E1tVNUw-0005tO-8H@fencepost.gnu.org>
Hi Richard,
On Tue, 07 Jan 2025 at 23:16, Richard Stallman <rms@gnu.org> wrote:
> The task here is to distribute Info manuals in a few
> platform-independent non-source forms, perhaps Info and HTML. Perhaps
> PDF files too. That is so much simpler than what Guix has to do that
> using Guix for this would be a quick and dirty hack.
>
> The task here can be done with something much simpler, and if we
> decide to do it, writing a clean solution won't take very long.
> And it will be simpler to understand than Guix.
I am not sure to understand: This list is guix-devel hence we speak
about using Guix for many tasks. :-)
Even more, I am convinced that GNU Guix is a perfect basis for
distributing GNU packages to heterogeneous platforms which do not use
Guix themselves. For instance, see command ’guix pack’ [1].
BTW, you wrote: « Guix is a GNU/Linux distribution, designed for
building packages. » and IMHO it’s a partial view of what Guix is.
Guix is a tool for composing and sharing computational environments; and
building packages is one brick. Well, for me, the best explanation of
what Guix means is to say “The Emacs of Distros” [2]. As written in
Guile manual (9.1.1 The Emacs Thesis):
Emacs, when it was first created in its GNU form in 1984, was a new
take on the problem of “how to make a program”. The Emacs thesis is
that it is delightful to create composite programs based on an
orthogonal kernel written in a low-level language together with a
powerful, high-level extension language.
And Guix follows this Emacs thesis at the scale of a computational
environment, IHMO. Where the “kernel” reads ’guix-daemon’ processing
derivations [3] and “high-level language” reads Guile/Scheme.
1: https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-pack
2: https://archive.fosdem.org/2015/schedule/event/the_emacs_of_distros/
3: https://guix.gnu.org/manual/devel/en/guix.html#Derivations
Cheers,
simon
next prev parent reply other threads:[~2025-01-09 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 22:34 GNU Manuals in Info/HTML format via Guix? Jeremy Bryant
2024-12-16 0:58 ` Suhail Singh
2024-12-16 21:36 ` Cayetano Santos
2024-12-18 1:20 ` Maxim Cournoyer
2025-01-02 7:29 ` Divya Ranjan
2024-12-19 19:56 ` Divya Ranjan
2024-12-19 20:56 ` Björn Bidar
2025-01-06 19:25 ` Simon Tournier
2025-01-08 4:16 ` Richard Stallman
2025-01-08 4:46 ` Divya Ranjan
2025-01-08 7:49 ` Suhail Singh
2025-01-08 23:11 ` Jeremy Bryant
2025-01-09 11:32 ` Simon Tournier [this message]
2025-01-09 16:46 ` Rostislav Svoboda
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=878qrk5ikm.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=arne_bab@web.de \
--cc=bjorn.bidar@thaodan.de \
--cc=guix-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=rms@gnu.org \
--cc=suhailsingh247@gmail.com \
/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).