unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Guile web page docs
Date: Thu, 29 Oct 2009 09:26:13 +0100	[thread overview]
Message-ID: <m3ocnqhahm.fsf@pobox.com> (raw)
In-Reply-To: <87pr879kc5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 29 Oct 2009 00:20:42 +0100")

On Thu 29 Oct 2009 00:20, ludo@gnu.org (Ludovic Courtès) writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>>>>>> (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.
>
> Hmm, OK.  I’ve never actually used it and I didn’t know that.
>
>> We could make Guile conform to those assumptions, but I'm not sure it's
>> worth it.
>
> Agreed.
>
>> 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.)
>
> That’s what I’ve been doing so far.  It’s slightly tedious because run
> gendocs.sh with the right parameters, have a cvs checkout, copy files
> there, add the new ones (and ideally remove the obsolete ones), then
> check-in and wait for ages.

It's possible to automate this. The crux of it is "cvs import" :)

dir=~/src/guile-gnome/platform/gtk/doc/gtk
file=guile-gnome-gtk

all:
	@echo "try make update"

index.html: %.html: %.scm
	( guile --debug -l $< -c '(make-index)' > $@ || { rm $@; false; } )

update: index.html
	rm -rf html
	( export tmp=`mktemp -d`; \
	  export cur=`pwd`; \
	  cd $$tmp; \
	  mkdir $(file); \
	  cp -a $(dir)/*.texi $(file)/; \
	  tar czvf $(file).texi.tar.gz $(file); \
	  cp $(file).texi.tar.gz $$cur/; \
	  cd $(file); \
	  makeinfo $(file).texi; \
	  tar czvf $(file).info.tar.gz $(file).info*; \
	  cp $(file).info.tar.gz $$cur/; \
	  makeinfo -o $$cur/html --html $(file).texi; \
	  texi2dvi -o $(file).dvi -q $(file).texi; \
	  dvips $(file) -o; \
	  gzip -9 $(file).ps; \
	  cp $(file).ps.gz $$cur/; \
	  gzip -9 $(file).dvi; \
	  cp $(file).dvi.gz $$cur/; \
	  texi2pdf --pdf -o $$cur/$(file).pdf -q $(file).texi; \
	  cd $$cur; \
	  rm -rf $$tmp; \
	)
	( export CVSDIR=$(shell cat ../CVS/Root); cvs -d $$CVSDIR import -m 'update manual' guile-gnome/docs/$(shell basename `pwd`) gnu $(shell date "+D%Y%m%d%H%M%S"))

-- 
http://wingolog.org/




      reply	other threads:[~2009-10-29  8:26 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
2009-10-28 23:20           ` Ludovic Courtès
2009-10-29  8:26             ` Andy Wingo [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://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=m3ocnqhahm.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=neil@ossau.uklinux.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.
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).