From: Divya Ranjan <divya@subvertising.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: guix-devel@gnu.org, "Richard Stallman" <rms@gnu.org>,
"Björn Bidar" <bjorn.bidar@thaodan.de>,
"arne_bab@web.de" <arne_bab@web.de>,
"Suhail Singh" <suhailsingh247@gmail.com>
Subject: Re: GNU Manuals in Info/HTML format via Guix?
Date: Thu, 19 Dec 2024 19:56:23 +0000 [thread overview]
Message-ID: <874j2zphug.fsf@subvertising.org> (raw)
In-Reply-To: <87r068bmom.fsf@jeremybryant.net> (Jeremy Bryant's message of "Sun, 15 Dec 2024 22:34:17 +0000")
Hello, Jeremy,
Jeremy Bryant <jb@jeremybryant.net> writes:
> Hi Guix developers,
>
> The GNU Project's documentation format is Texinfo.
> How about distributing some or many Texinfo manuals through Guix, is
> this something that is consistent with previous norms in Guix?
I believe this is certainly feasible, and desirable. Since Guix itself relies a lot on functioning with info for its documentation requirements.
> Following a discussion on emacs-devel, several people suggested that
> GNU Guix may be a a good way to contemplate this distribution mechanism,
> for obvious GNU-related reasons.
>
> We discussed both a comprehensive solution for Info manuals, as well as
> specific cases such as RMS's C manual (c.info) which is not part of a
> software project.
As Maxim noted, the particular manual already exists. But we need to think about how exactly to package the Info manuals. Since Guix’s process of packaging is a bit differently organized, we’d have to figure out where exactly should the package definitions for these manuals live in the Guix source tree. I see that the C manual is in gnu/packages/c.scm and SICP in gnu/packages/scheme.scm, so maybe each manual could go into the relevant program/language’s guile module. Or, should we have a module just for the Info manuals? I see gnu/packages/texinfo.scm and it has mostly a few packages related to TeXinfo readers, could we put them there, or only the miscellaneous ones?
Those more knowledgeable about Guix’s source-tree management should shed light on this.
Regards,
--
Divya Ranjan,
Philosophy, Mathematics, Libre Software.
next prev parent reply other threads:[~2024-12-19 19:57 UTC|newest]
Thread overview: 6+ 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
2024-12-19 19:56 ` Divya Ranjan [this message]
2024-12-19 20:56 ` Björn Bidar
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=874j2zphug.fsf@subvertising.org \
--to=divya@subvertising.org \
--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).