unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Jeremy Bryant <jb@jeremybryant.net>, guix-devel@gnu.org
Cc: "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: Mon, 06 Jan 2025 20:25:13 +0100	[thread overview]
Message-ID: <87ttabwxra.fsf@gmail.com> (raw)
In-Reply-To: <87r068bmom.fsf@jeremybryant.net>

Hi,

On Sun, 15 Dec 2024 at 22:34, Jeremy Bryant <jb@jeremybryant.net> wrote:

> 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?
>
> 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.

Some Info manuals which are not part of any software are distributed by
Guix; for example see the Guix package ’gnu-standards’.

Well, I think you are asking two questions. (1) Can Guix distribute
Texinfo manuals using another format as HTML?  Well, since ’makeinfo’
supports(*) HTML output, the answer seems yes. :-) Something under
share/html in addition to share/info; perhaps.

(2) Can we package any Texinfo manual and distribute it?  Yes.  Although
maybe it would require a dedicated build system in order to avoid each
time the same sequence of ’invoke’.

Cheers,
simon


(*) makeinfo --html: maybe we need to check if the Guix package of
    texinfo is correctly configured to output HTML.


  parent reply	other threads:[~2025-01-06 19:26 UTC|newest]

Thread overview: 12+ 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 [this message]
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

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=87ttabwxra.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).