     InDependence:  Tools for Dependency Tracking of RPM Packages
	  http://www.cse.ogi.edu/DISC/projects/independence/
	     Crispin Cowan, Hao Zhao, and Ryan Finnin Day
      crispin@cse.ogi.edu, haoz@microsoft.com, rday@csmonitor.com

For installation, see the COPYING file.

For detailed documentation, see the "dep" and "rpmtc" man pages.

InDependence is a suite of tools (well two :-) designed to help RPM
packagers and system administrators deal with the dependencies between
RPM packages.  InDependence has two major components:

Dep:  This tool is for the RPM packager that identifies external files
    or RPM packages that a program uses.  Dep is a command-line
    "wrapper", similar to the "time" command, i.e. to determine which
    files and packages the foo command uses, you would say:

    	dep foo <foo's argument list>
    
    foo will then run normally.  However, dep will use strace to wrap
    the foo command, and record all of the files that foo accesses.
    Following completion of the foo command, dep sorts & filters the
    list of accessed files, eliminates duplicates, identifies the
    RPM package that owns any of the files accessed, and drops the
    result into ~/.dep/foo.

    Dep accumulates results, i.e. multiple runs of the foo command
    using different arguments and inputs will accumulate additional
    files accessed into ~/.dep/foo without deleting the previous list.

    The RPM packager can thus exercise a candidate program under
    whatever test suite is deemed suitable, and dep will record all of
    the files accessed, and identify the RPM packages that own that
    file.

    The result is that following testing, the RPM packager can state
    with confidence the list of RPM packages and files that a given
    program depends on for correct operation.

RPMTC:	"RPM Transitive Closure".  This tool is for the RPM system
    administrator.  "rpmtc foo.rpm" will transitively compute the
    *entire* set of RPMs necessary to support the foo.rpm package, i.e.
    if foo.rpm depends on bar.rpm, and bar.rpm depends on baz.rpm,
    RPMTC will report both bar and baz.

    RPMTC supports options to query either the installed RPM database,
    or a file system directory populated with RPM files.
