all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Divya Ranjan <divya@subvertising.org>
Cc: Jeremy Bryant <jb@jeremybryant.net>,
	 guix-devel@gnu.org,  Richard Stallman <rms@gnu.org>,
	 "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 22:56:43 +0200	[thread overview]
Message-ID: <87msgrtmr8.fsf@> (raw)
In-Reply-To: <874j2zphug.fsf@subvertising.org> (Divya Ranjan's message of "Thu, 19 Dec 2024 19:56:23 +0000")


First of all I want to quickly write that I was staying quite as I'm not
a Guix guy but just interested in extending and improving the distribution
of info manuals.

Divya Ranjan <divya@subvertising.org> writes:

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

I think Guix could serve as the showcase project on how to best
integrate and distribute info manuals in distributions.
For my efforts that Guix has been that. If I was looking for an info
manual for something it almost all the time I found it at Guix.
The only exception was the manual of Lua but for that one there was only
one manual conversion very long time ago.


      reply	other threads:[~2024-12-19 21:12 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
2024-12-19 20:56   ` Björn Bidar [this message]

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=87msgrtmr8.fsf@ \
    --to=bjorn.bidar@thaodan.de \
    --cc=arne_bab@web.de \
    --cc=divya@subvertising.org \
    --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 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.