rcorder(8) [netbsd man page]

RCORDER(8)						    BSD System Manager's Manual 						RCORDER(8)

NAME

     rcorder -- print a dependency ordering of interdependent files

SYNOPSIS

     rcorder [-k keep] [-s skip] file ...

DESCRIPTION

     rcorder is designed to print out a dependency ordering of a set of interdependent files.  Typically it is used to find an execution sequence
     for a set of shell scripts in which certain files must be executed before others.

     Each file passed to rcorder should be annotated with special lines (which look like comments to the shell) which indicate the dependencies
     the files have upon certain points in the sequence, known as ``conditions'', and which indicate, for each file, which ``conditions'' may be
     expected to be filled by that file.

     Within each file, a block containing a series of ``REQUIRE'', ``PROVIDE'', ``BEFORE'' and ``KEYWORD'' lines should appear.  The format of the
     lines is rigid.  Each line must begin with a single ``#'', followed by a single space, followed by ``PROVIDE:'', ``REQUIRE:'', ``BEFORE:'',
     or ``KEYWORD:''.  No deviation is permitted.  Each dependency line is then followed by a series of conditions, separated by whitespace.  Mul-
     tiple ``PROVIDE'', ``REQUIRE'', ``BEFORE'' and ``KEYWORD'' lines may appear, but all such lines must appear in a sequence without any inter-
     vening lines, as once a line that does not follow the format is reached, parsing stops.

     The options are as follows:

     -k      Add the specified keyword to the ``keep list''.  If any -k option is given, only those files containing the matching keyword are
	     listed.

     -s      Add the specified keyword to the ``skip list''.  If any -s option is given, files containing the matching keyword are not listed.

      An example block follows:

	   # REQUIRE: networking syslog
	   # REQUIRE: usr
	   # PROVIDE: dns nscd

     This block states that the file in which it appears depends upon the ``networking'', ``syslog'', and ``usr'' conditions, and provides the
     ``dns'' and ``nscd'' conditions.

     A file may contain zero ``PROVIDE'' lines, in which case it provides no conditions, and may contain zero ``REQUIRE'' lines, in which case it
     has no dependencies.  A file containing no ``PROVIDE'', ``REQUIRE'', or ``BEFORE'' lines may be output at an arbitrary position in the depen-
     dency ordering.

     There must be at least one file with no dependencies in the set of arguments passed to rcorder in order for it to find a starting place in
     the dependency ordering.

DIAGNOSTICS

     rcorder may print one of the following error messages and exit with a non-zero status if it encounters an error while processing the file
     list.

     Requirement %s has no providers, aborting.  No file has a ``PROVIDE'' line corresponding to a condition present in a ``REQUIRE'' line in
     another file.

     Circular dependency on provision %s, aborting.  A set of files has a circular dependency which was detected while processing the stated con-
     dition.

     Circular dependency on file %s, aborting.	A set of files has a circular dependency which was detected while processing the stated file.

SEE ALSO

     rc(8)

HISTORY

     The rcorder program first appeared in NetBSD 1.5.

AUTHORS

     Written by Perry E. Metzger <perry@piermont.com> and Matthew R. Green <mrg@eterna.com.au>.

BSD
								  April 23, 2003							       BSD

Check Out this Related Man Page

md(1)							    BSD General Commands Manual 						     md(1)

NAME

     md -- process raw dependency files produced by cpp -MD

SYNOPSIS

     md [-d] [-f] [-m makefile] [-u makefile] [-o outputfile] [-v] [-x] [-D c|d|m|o|t|D]

DESCRIPTION

     The md command basically does two things:

     Process the raw dependency files produced by the cpp -MD option.  There is one line in the file for every #include encountered, but there are
     repeats and patterns like .../dir1/../dir2 that appear which should reduce to .../dir2.  md canonicalizes and flushes repeats from the depen-
     dency list.  It also sorts the file names and "fills" them to a 78 character line.

     md also updates the makefile directly with the dependency information, so the .d file can be thrown away (see d option).  This is done to
     save space.  md assumes that dependency information in the makefile is sorted by .o file name and it procedes to merge in (add/or replace [as
     appropriate]) the new dependency lines that it has generated.  For time effeciency, md assumes that any .d files it is given that were cre-
     ated before the creation date of the "makefile" were processed already.  It ignores them unless the force flag [f] is given.

FLAG SUMMARY

     -d delete the .d file after it is processed

     -f force an update of the dependencies in the makefile even though the makefile is more recent than the .n file (This implies that md has
     been run already.)

     -m makefile specify the makefile to be upgraded.  The defaults are makefile and then Makefile

     -u makefile like -m above, but the file will be created if necessary

     -o outputfile specify an output file for the dependencies other than a makefile

     -v set the verbose flag

     -x expunge old dependency info from makefile

     -D c|d|m|o|t|D subswitch for debugging.  can be followed by any of "c", "d", "m", "o", "t", "D" meaning:

	      c       show file contents
	      d       show new dependency crunching
	      m       show generation of makefile
	      o       show files being opened
	      t       show time comparisons
	      D       show very low level debugging

SEE ALSO

     make(1)

BUGS

     Old, possibly not used by anyone.

HISTORY

     The md utility was written by Robert V Baron at Carnegie-Mellon University.

BSD
								   June 2, 2019 							       BSD

Linux and UNIX Man Pages

rcorder(8) [netbsd man page]

Check Out this Related Man Page