From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Antero Mejr <antero@mailbox.org>
Cc: 62554@debbugs.gnu.org
Subject: [bug#62554] [PATCH] gnu: Add book-r5rs.
Date: Sun, 09 Apr 2023 13:41:06 +0800 [thread overview]
Message-ID: <878rf1k3yl.fsf@envs.net> (raw)
In-Reply-To: <20230331032841.27505-1-antero@mailbox.org> (Antero Mejr's message of "Fri, 31 Mar 2023 03:28:41 +0000")
Antero Mejr <antero@mailbox.org> writes:
> * gnu/packages/book-software.scm (book-r5rs): New variable.
> ---
> Please apply this patch last.
> This patch is for the R5RS spec document, in PDF and Info formats.
> Not sure what conventions would work best, but here I used:
> 1. package definitions for books/documents go into the file
> "book-[type].scm".
> 2. package definition names are formatted "book-[shortname]".
Good idea, I'll rename 'faif' to 'book-faif' later.
> I would be interested to hear what others think about books in Guix.
> Would we want to limit to technical books? What about translations?
> Has this already been proposed somewhere?
I don't know any former proposed/discussion. Well I'd like to also
include translations, eg:
https://github.com/lifanxi/free-as-in-freedom-zh-cn
https://github.com/beijinglug/fsfs-zh
For non-technical books, maybe math books? eg:
https://discrete.openmathbooks.org/dmoi3.html
I'm not sure though, due to lack of confidence to make a judge...
next prev parent reply other threads:[~2023-04-09 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 3:28 [bug#62554] [PATCH] gnu: Add book-r5rs Antero Mejr via Guix-patches via
2023-03-31 3:36 ` [bug#62554] [PATCH 1/3] gnu: Add rrrs2txi Antero Mejr via Guix-patches via
2023-03-31 3:36 ` [bug#62554] [PATCH 2/3] teams: Add book team Antero Mejr via Guix-patches via
2023-03-31 3:36 ` [bug#62554] [PATCH 3/3] teams: Add Antero Mejr Antero Mejr via Guix-patches via
2023-04-09 5:41 ` 宋文武 via Guix-patches via [this message]
2023-04-18 1:30 ` [bug#62554] [PATCH] gnu: Add book-r5rs Antero Mejr via Guix-patches via
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=878rf1k3yl.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=62554@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=iyzsong@envs.net \
/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.