From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile web page docs
Date: Wed, 28 Oct 2009 22:53:02 +0000 [thread overview]
Message-ID: <87tyxj871t.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ocnupp2a.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 26 Oct 2009 07:55:09 +0000")
>>>> (BTW, Gnulib has a new script to automate updates to
>>>> www.gnu.org/software/PROJECT/manual.)
>>>
>>> Right; I assume you mean gendocs.sh.
>>
>> I was thinking about the ‘gnu-web-doc-update’ module.
>
> I'll take a look, thanks.
[guile-user trimmed]
This doesn't look so useful to me. It makes assumptions about the
package that don't hold for Guile: a bootstrap script (our autogen.sh);
manual in doc/manual; and a `make web-manual' Makefile target.
We could make Guile conform to those assumptions, but I'm not sure it's
worth it. Isn't it already pretty easy to use gendocs.sh, copy the
generated files into the web-pages tree, and commit? (I've actually
never used gendocs.sh.)
Certainly for the 1.9/2.0 docs, it's trivial to just do `make html'
followed by `cp -a doc/ref/guile.html ../web-pages/docs/master/'.
Neil
next prev parent reply other threads:[~2009-10-28 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 20:47 Guile web page docs Neil Jerram
2009-10-21 21:25 ` Ludovic Courtès
2009-10-23 22:25 ` Neil Jerram
2009-10-25 18:56 ` Ludovic Courtès
2009-10-26 7:55 ` Neil Jerram
2009-10-27 22:46 ` Neil Jerram
2009-10-28 22:53 ` Neil Jerram [this message]
2009-10-28 23:20 ` Ludovic Courtès
2009-10-29 8:26 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tyxj871t.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
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).