unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Divya Ranjan <divya@subvertising.org>
To: guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Cayetano Santos <csantosb@inventati.org>
Cc: "Jeremy Bryant" <jb@jeremybryant.net>,
	"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, 02 Jan 2025 07:29:32 +0000	[thread overview]
Message-ID: <904C57EE-BA57-43AE-BF3E-A7657B92CA63@subvertising.org> (raw)
In-Reply-To: <87y10drdl1.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]

I plan to begin working towards this to package GNU Manuals. But, I wish to ask, where should I collect these manuals from? They aren't at a centralized place, I guess? So I should look for them one-by-one through the FSF Directory?

And Guix users/devs, is there a way to figure our whether a GNU Manual is already packaged with its parent package (of which it is a manual) or not?


I plan to first port them to my Guix channel [0] and then send patches upstream.

[0]: https://codeberg.org/divyaranjan/divya-lambda

Regards,

On 18 December 2024 01:20:58 GMT, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>Hello,
>
>Cayetano Santos <csantosb@inventati.org> writes:
>
>>>dim. 15 déc. 2024 at 22:34, Jeremy Bryant <jb@jeremybryant.net> wrote:
>>
>>> 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.
>>
>> Remember you always have the possibility to create a dedicated guix
>> channel, external but complementary to guix upstream itself, to
>> distribute manuals. This would about any additional overload on guix
>> maintenance tasks.
>
>Well, the topic being GNU manuals, they'd be more than at home in GNU
>Guix.  Typically though they come with the packages themselves, such as
>'libc.info.gz' which is shipped with glibc.
>
>I think Guix would be a fine place to have them packaged and made
>available.  We already have the C manual you mentioned; it's a great
>read!  You can read it with
>
>--8<---------------cut here---------------start------------->8---
>$ guix shell info-reader c-intro-and-ref -- info c'
>--8<---------------cut here---------------end--------------->8---
>
>More info on this package:
>
>--8<---------------cut here---------------start------------->8---
>$ guix show c-intro-and-ref
>name: c-intro-and-ref
>version: 0.0.0-1.47e5a23
>outputs:
>+ out: tout
>systems: x86_64-linux i686-linux
>dependencies: texinfo@6.8
>location: gnu/packages/c.scm:83:4
>homepage: https://www.gnu.org/
>license: FDL 1.3+
>synopsis: GNU C Language Intro and Reference  
>description: This manual explains the C language for use with the GNU Compiler Collection (GCC) on the
>+ GNU/Linux system and other systems.  We refer to this dialect as GNU C.  If you already know C, you can use
>+ this as a reference manual.
>--8<---------------cut here---------------end--------------->8---
>
>-- 
>Thanks,
>Maxim
>

Divya Ranjan, Mathematics, Philosophy and Libre Software

[-- Attachment #2: Type: text/html, Size: 3565 bytes --]

  reply	other threads:[~2025-01-02  7:30 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 [this message]
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
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=904C57EE-BA57-43AE-BF3E-A7657B92CA63@subvertising.org \
    --to=divya@subvertising.org \
    --cc=arne_bab@web.de \
    --cc=bjorn.bidar@thaodan.de \
    --cc=csantosb@inventati.org \
    --cc=guix-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=maxim.cournoyer@gmail.com \
    --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).