From: Suhail Singh <suhailsingh247@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
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: Wed, 08 Jan 2025 02:49:53 -0500 [thread overview]
Message-ID: <875xmpd9su.fsf@gmail.com> (raw)
In-Reply-To: <E1tVNUw-0005tO-8H@fencepost.gnu.org> (Richard Stallman's message of "Tue, 07 Jan 2025 23:16:50 -0500")
Richard Stallman <rms@gnu.org> writes:
> That is so much simpler than what Guix has to do that using Guix for
> this would be a quick and dirty hack.
There's no denying that using Guix isn't necessary. However, to be
clear, Guix does already distribute Info manuals (standalone and
otherwise) today. While not necessary, I don't see why using Guix
package manager would be a "dirty hack".
> The task here can be done with something much simpler
Even for those manuals that would require conversion from a different
documentation system such as Sphinx? What do you propose ought to be
used to manage the build environment needs for such tasks?
--
Suhail
next prev parent reply other threads:[~2025-01-08 7:51 UTC|newest]
Thread overview: 13+ 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 [this message]
2025-01-08 23:11 ` Jeremy Bryant
2025-01-09 11:32 ` Simon Tournier
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=875xmpd9su.fsf@gmail.com \
--to=suhailsingh247@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=zimon.toutoune@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).