rpmspec: a utility to update the rpm database from a spec file

rpmspec solves one problem, which may have applicability in a number of
circumstances.  Using the contents of a properly-formed .spec file, rpmspec
can update the database.  This sidesteps several of the usual guarantees of
the rpm utility.  It does so deliberately.

rpmspec can be used to sidestep problems or restrictions in the usual rpm
utility.  If an installation utility is both willing to install files
itself, and to update a .spec file with the appropriate information, rpmspec
can then manage the update of the database, without requiring that a proper
.rpm file be created.

This is useful in these circumstances: 1) the installation of the files
happened before rpm was installed (for instance, the base system for an OS
that rpm is being extended to, especially if that OS is proprietary).  2)
the installation needs to be more flexible than rpm normally provides
(installing files conditionally, installing to different than "standard"
locations).  3) the builder of a regular .rpm package wants to test a .spec
file, without the dreary labor of uninstalling, and passing through all the
steps required to build.

Let it be noted, however, that any sidestepping of rpm carries with it
potential dangers, and abuse of this utility will rapidly lead to the sort
of confusion and despair common for well-distributed platforms that don't
have a system installer.  Use it wisely, and that means *parsimoniously*.

There are some reservations on how the spec file must look.  First, shell
globs are not supported, under any circumstances.  *, ?, [whatever], or any
of the other glob characters, are interpreted as specific names, not as
globs.  The reason for this restriction is because rpmspec doesn't do the
actual installation itself, and it really just wouldn't do to let someone
specify that they own all the files in /usr/bin.  In this regard, rpmspec
sort of demands that all the files be specified to the level of detail that
they would have in the package cpio archive.

On the other hand, it is generally permissible to use the %doc shorthand
with relative paths (as long as the paths do not include globs, that is). 
rpmspec will expand this material to use the actual name of the default
documentation  directory.

aal 02/21/00
cog 07/15/00
