Description of problem:
RPM's man page info on --initdb implies that any existing RPM database will be
replaced by a new, empty database.  Possibly this used to be the effect, but
currently --initdb only ensures that an RPM database is present (in fact, just
the Packages file), and doesn't do anything if the database already exists. 
Therefore it is safe and unnecessary to do an --initdb at any time, such as just
before a --rebuilddb.

The man page section on --initdb could say:

"Use --initdb to ensure that the database exists, without changing any existing
database; use --rebuilddb to rebuild the database indices from the installed
package headers in the Packages file."

Version-Release number of selected component (if applicable):
rpm-4.4.2-32.i386

How reproducible:


Steps to Reproduce:
1. man rpm
2.
3.
  
Actual results:


Expected results:


Additional info: