>From sfwnv-discuss-bounces at opensolaris.org Wed Feb 27 11:31:58 2008
>> Yes, it does mean knowing what those bits are. If it delivers a new
>> file or stops delivering a file, you will find out the first time you
>> run nightly(1). The proto area and packages won't match. If you cherry
>
>Not so.
yes so.
>nightly in SFW does no unref file checks,
which has nothing to do with pkgmk/protocmp. The unref check
looks for unreferenced source files, it doesn't look at the proto
area afaik. That check isn't as useful in SFW as it is in ON, since
most of the source is from the tar files and there may well be a lot
of unreferenced bits because they are for other platforms or options
(though it might ignore files that aren't under SCCS control).
>I think (I haven't
>run nightly(1) yet,
well I'm glad you know it wouldn't have found a problem then :)
>but I don't see any files in the nametable that
>would allow one to list unreferenced files).
when nightly builds packages, if you told pkgmk to package a file
that you didn't put in the proto area it will fail and stop the package
build. by default it will run protocmp too, which will compare the
proto area to the pkgdefs and tell you if things are different (files
in the proto area that aren't packaged, files that are packaged but
not in the proto area, and files that differ). Assuming you aren't using
nightly's -N flag, which you better not use.
Mike
