From: Alex Kost <alezost@gmail.com>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: 22543@debbugs.gnu.org
Subject: bug#22543: 404 in Manualpage
Date: Wed, 17 Feb 2016 12:29:25 +0300 [thread overview]
Message-ID: <87si0rlm6i.fsf@gmail.com> (raw)
In-Reply-To: <87k2m5vv0q.fsf@grrlz.net> (Nils Gillmann's message of "Tue, 16 Feb 2016 10:56:05 +0100")
Nils Gillmann (2016-02-16 12:56 +0300) wrote:
>>> I don't think you can send a patch for this. According to
>>> <https://www.gnu.org/software/guix/manual/>:
>>>
>>> (This page generated by the gendocs.sh¹ script.)
>
>>> This "gendocs.sh" uses "texi2html" to convert our texinfo documentation
>>> (see "doc/guix.texi" in the guix git repo) to the html page. In
>>> "guix.texi" the link you are talking about is a usual link to the
>>> "gnutls-guile" manual. I didn't look at "texi2html" but I believe by
>>> default it just assumes that all the manuals are placed at
>>> "www.gnu.org/software/<package>/manual/", so for "external" manuals the
>>> generated links are false. For example, there are also wrong links to
>>> Geiser and Magit-Popup manuals.
>>>
>>> So I think it's a general thing for all generated manuals that are
>>> placed on "gnu.org".
>>>
>>> ¹ http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gendocs.sh
>
> Okay, so I guess it's related to #22651 and it#s not fixable the
> way I want to (edit the source), or at least what I would want to
> do is not optimal and it should be fixed in some other way.
>
> Didn't look into it yet, but should we follow #22651 for the 404s?
As I see it, these issues about online manual are totally unrelated to
Guix itself. If there is something to do about it, it should be done in
some other place (where .texi files are converted into html pages for
gnu.org).
--
Alex
next prev parent reply other threads:[~2016-02-17 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:41 bug#22543: 404 in Manualpage Nils Gillmann
2016-02-13 0:26 ` Leo Famulari
2016-02-16 9:56 ` Nils Gillmann
2016-02-17 9:29 ` Alex Kost [this message]
2016-02-14 11:15 ` Alex Kost
2016-02-21 21:30 ` Ludovic Courtès
2016-02-22 11:31 ` Alex Kost
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=87si0rlm6i.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22543@debbugs.gnu.org \
--cc=niasterisk@grrlz.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.