Arun Isaac <arunisaac@systemreboot.net> writes:

>>> I think we shouldn't install documentation. A markdown README, IMHO, is
>>> not much of a documentation. No other package does this. WDYT?

By the way while I tried to find a way to convert Markdown to texinfo or
info I found “/gnu/store/…-markdown-1.0.1/share/doc/README”.

Also gives many of README
--8<---------------cut here---------------start------------->8---
find /gnu/store -name README
--8<---------------cut here---------------end--------------->8---

>> Personally, I usually read README, even if it's not presented in
>> package, but on home-page, because it helps me to configure quickly.
>
> Yes, I do read the README too, but only from the project's website.
>
>> So, maybe we could have them or convert them in “info” or something?
>
> That would be nice! But, how do we do that? My guess is that we'll have
> to contact upstream, and ask them to create "an info file". Is there
> some other way?

I don't think it will be possible to contact every maintainer (for other
packages).  And I didn't find a tool to convert, too.  As I understand
it preferably needs to be written in Guile or C.  There are famous
things like Pandoc which will pull all Haskell or whatever language.
Obvios over powered for Emacs packages.

So, if you don't think it's proper for Guix, then here is a patch
without README.