Hi Dmitriy,
> It seems that I've solved compatibility problems with strings and bytes. It
> was too late, Bruno, when your letter came
I try to answer rapidly, but sometimes it takes me longer. Sorry about that.
> Now there is another question. I need to get some information about
> command-line options. It would be great if you tell me some details:
> 1) --list, --find, --import, --add-import, --remove-import, --update,
> --create-testdir, --create-megatestdir, --test, --copy-file, --extract-*.
> Are they overwriting? i.e. can only one option be set? As I see from source
> code, there is variable mode which is set equivalent to mode, but I need to
> be sure.
The "gnulib-tool --usage" text lists these as different "operation modes"
(together with --help and --version). This means that exactly one of these
options should be given.
Currently the last one to be mentioned "wins". This is suboptimal; it would
be better to reject command lines like
./gnulib-tool --extract-description --list
or
./gnulib-tool --import --find
The only exception to this rule is that '--help' may win against all others.
(Many GNU programs work like this, try 'ls --help -l' and 'ls -l --help'.)
I hope this is easier to implement in Python than it would be in shell script.
> 2) I need all what you can say about other arguments. It would be great if
> there is something like architecture.odg and functions.odt files, but I'll
> be very grateful for any information.
The "gnulib-tool --usage" text tries to say it:
- "Operation mode" means that exactly one of these should be specified.
- "General options" means options that can apply to all modes.
- "Options for --import, --add/remove-import, --update" are allowed
only for --import, --add-import, --remove-import, --update. Etc.
Bruno