bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnu-web-doc-update: fails to add new directories


From: Akim Demaille
Subject: gnu-web-doc-update: fails to add new directories
Date: Thu, 13 Dec 2012 09:14:31 +0100

Hi!

The Bison's documentation now uses images, including in HTML.  gendocs.sh 
properly sets up a directory with the images for all the documentation formats. 
 Unfortunately gnu-web-doc-update fails to add all the new files, because it 
fails to discover new directories.

My CVS-skills are, ahem, rusty, and I have never been a cvsutils user, so I 
don't know if the bug is in cvsu or gnu-web-doc-update, but the problem is in 
these bits:

(
  cd $tmp/$pkg/manual

  # Add any new files:
  $CVSU --types='?'                             \
    | sed s/..//                                \
    | $XARGS --no-run-if-empty -- $CVS add -ko

  $CVS ci -m $version
)

in Bison's case, the unknown directories are not reported as "?", but as "D":

address@hidden ..2.5/web-doc-update.grDYlq/bison/manual $ cvs status
? figs
? html_node/figs
cvs status: Examining .
===================================================================
File: bison.dvi.gz      Status: Needs Patch
[…]

address@hidden ..2.5/web-doc-update.grDYlq/bison/manual $ cvsu '--types=?'
address@hidden ..2.5/web-doc-update.grDYlq/bison/manual $ cvsu
D figs
D html_node/figs
address@hidden ..2.5/web-doc-update.grDYlq/bison/manual $ cvs add figs
? figs/example-reduce.png
? figs/example-shift.png
? figs/example.png
Triggering webpages update...
Directory /webcvs/bison/bison/manual/figs added to the repository
address@hidden ..2.5/web-doc-update.grDYlq/bison/manual $ cvsu
? figs/example-reduce.png
? figs/example-shift.png
? figs/example.png
D html_node/figs
address@hidden ../bison-2.5/web-doc-update.grDYlq/bison $ cvsu --type=D
D manual/html_node/figs


So I don't know if gnu-web-doc-update should learn about --type=D,
or if cvsu should mention unknown directories with '?'.

Cheers!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]