From: Antero Mejr via Guix-patches via <guix-patches@gnu.org>
To: 宋文武 <iyzsong@envs.net>
Cc: 62554@debbugs.gnu.org
Subject: [bug#62554] [PATCH] gnu: Add book-r5rs.
Date: Tue, 18 Apr 2023 01:30:55 +0000 [thread overview]
Message-ID: <87r0sigenk.fsf@mailbox.org> (raw)
In-Reply-To: <878rf1k3yl.fsf@envs.net> ("宋文武"'s message of "Sun, 09 Apr 2023 13:41:06 +0800")
宋文武 <iyzsong@envs.net> writes:
>> 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.
Do you think it would be a good idea to install the files to
/share/doc/[shortname]/, or just /share/doc/? I used the first one to
avoid cluttering /share/doc/, or maybe for organization purposes if a
book is split into multiple files. But I can update this patch to use
/share/doc/ if you disagree.
>> 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
Sounds good to me.
> 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...
I would definitely want math books. I would be OK with any non-fiction
work so long as it can be typeset from source and is freely licensed,
but then there might be a lot of book packages.
prev parent reply other threads:[~2023-04-18 1:32 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 ` [bug#62554] [PATCH] gnu: Add book-r5rs 宋文武 via Guix-patches via
2023-04-18 1:30 ` Antero Mejr via Guix-patches via [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
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=87r0sigenk.fsf@mailbox.org \
--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 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).