On Wed, Feb 27, 2008 at 11:40:33AM -0800, mike.sullivan at sun.com wrote: > >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.
How? If I install straight into $ROOT and new things are delivered and nightly doesn't check for things in $ROOT not referenced by any prototype files in $SRC/pkgdefs/*, then how will nightly(1) know? > >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 That's NOT what the quoted text above was about -- it's about new files in $ROOT, not new unreferenced files in $SRC. > 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). Which means that nightly(1), indeed, will not complain about new, unreferenced files in the proto. > >I think (I haven't > >run nightly(1) yet, > > well I'm glad you know it wouldn't have found a problem then :) It won't find unref files in the PROTO, that's clear (and you agree). > >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 Yes, this I know. I'm talking about new items in proto, not missing ones.
