From: Suhail Singh <suhailsingh247@gmail.com>
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: Sun, 15 Dec 2024 19:58:06 -0500 [thread overview]
Message-ID: <87zfkwculd.fsf@gmail.com> (raw)
In-Reply-To: <87r068bmom.fsf@jeremybryant.net> (Jeremy Bryant's message of "Sun, 15 Dec 2024 22:34:17 +0000")
Jeremy Bryant <jb@jeremybryant.net> writes:
> 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?
Guix has had SICP available via Info format since 2016:
<https://packages.guix.gnu.org/packages/sicp/20180718-3.bda03f7/>. The
Info file is built directly from the Texinfo source by invoking
makeinfo:
<https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/scheme.scm#n626>.
Packaging becomes even easier when the Texinfo source is available as an
ELPA package. For comparison, I created a patch for the similar sicp
Emacs package (<https://github.com/webframp/sicp-info>):
<https://issues.guix.gnu.org/74906>.
The package definition is somewhat simpler since it obviates the manual
invocation of makeinfo.
> 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.
>
> WDYT?
Given a standalone Texinfo source that we want to distribute as an Info
manual, creating a corresponding ELPA package repository is especially
effective. It makes packaging into Guix easier. Additionally, it makes
the generated Info manual available to users of Emacs who don't use Guix
(via package-vc-install etc).
--
Suhail
parent reply other threads:[~2024-12-16 0:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87r068bmom.fsf@jeremybryant.net>]
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=87zfkwculd.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 \
/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.