Re: check-db script can not process --database argument correctly

Re: check-db script can not process --database argument correctly

[Milan Zamazal]

> The check-db script does not process the argument --database
> correctly, the argument gets parsed but the databases file is not
> scanned for the GNATSROOT and therefore the default directory is used.

--database in check-db works fine for me, I can't reproduce the problem
and can't see any reason why it shouldn't work.  I probably
misunderstood something, could you please describe the problem more
precisely?

> Second problem: more than one database argument seems to be ignored
> without checking the database.

According to the documentation, there seems to be no support for
multiple --database options in check-db.

Nevertheless I admit there should be an easy way to check all databases.
First, I thought it should be default behavior of check-db, but that
would be inconsistent with the general approach of using the default
database by default.  So I added a new option `--all-databases' to
check-db, it should appear in CVS soon.

Regards,

Milan Zamazal

-- 
  _/_\_/_  o     _\_/_\_  o     _/_\_/_  o     _\_/_\_  o    BEWARE!
-<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--   *Bugs* are
   / \ /   o      \ / \   o      / \ /   o      \ / \   o     approaching!