Karl Berry wrote:
> First, regarding gnulib-tool --help.
>
> --update isn't mentioned under "Operation modes:", although it is one
> of the usages.
I'm adding this doc:
--update update the current package, restore files omitted
from CVS
> I suggest mentioning that --import can also be used for updating,
> something like this (as I understand it from gnulib-tool.texi):
> --import import the given modules into the current package;
> if no modules are specified, update the
> current package.
I'll better write it this way:
--import import the given modules into the current package;
if no modules are specified, update the current
package from the current gnulib
The idea is that there are two meanings of "update", one related to CVS and
the other related to newer versions of gnulib, and the two require slightly
different logic. Like autopoint vs. gettextize.
Currently "gnulib-tool --import" and "gnulib-tool --update" do the same;
this will change when ChangeLog update support is added.
> Second, I tried gnulib-tool --dry-run --update and got this:
>
> gnulib-tool: invalid options for 'update' mode
> Try 'gnulib-tool --help' for more information.
> If you really want to modify the gnulib configuration of your project,
> you need to use 'gnulib --import' - at your own risk!
>
> I don't want to modify the configuration ...
Did you pass other options than --dry-run --update, such as --lib,
--source-base, --m4-base, --tests-base, --aux-dir, --with-tests, --avoid,
--lgpl, --macro-prefix? These options are only supported for --import,
not --update.
> Third, I tried gnulib-tool --dry-run --import and got this output:
> Module list with included dependencies:
>
> File list:
> lib/dummy.c
> m4/onceonly_2_57.m4
> Create directory ./lib
> Create directory ./m4
> cp: cannot create regular file `./lib/dummy.c.tmp': No such file or
> directory
> gnulib-tool: *** failed
> gnulib-tool: *** Stop.
Fixed. Thanks for the report.
Bruno
