findunref(1ONBLD) | illumos Build Tools | findunref(1ONBLD) |
The root of the source tree to examine is specified by srcroot. To simplify comparing findunref output from different source trees, findunref outputs all filenames relative to srcroot.
Some files in a source tree may be intentionally unreferenced (e.g., documentation) or only referenced during specialized types of builds. Accordingly, exceptfile names a file containing a list of pathname globs that will be ignored by findunref. Within exceptfile, any lines consisting solely of whitespace or starting with # will be ignored. Directory globs may also be specified, which will cause any matching directories to be skipped entirely. If no exceptions are desired, exceptfile can be /dev/null.
Depending on how findunref is invoked, it can either check all files, or limit its checks to files under control of a specific source code management (SCM) system.
To limit checks to files managed by Mercurial, the hg(1) utility must be present in $PATH and any relevant repositories must be located at or under srcroot. Nested Mercurial repositories are supported.
To limit checks to files managed by Git, the git(1) utility must be present in $PATH and any relevant repositories must be located at or under srcroot. Nested Git repositories are not supported.
comm -12 /path/to/unref-i386.out
/path/to/unref-sparc.out > unref.out
This merged file can then be compared against the gate's latest unreferenced file list (e.g. /ws/onnv-gate/usr/src/unrefmaster.out).
Different gates have different unreferenced file policies. Any changes to exceptfile that would define new unreferenced file policies for a given gate must be cleared with the appropriate gatekeepers.
October 30, 2012 |