>From Nicolas.Williams at sun.com Wed Feb 27 11:51:56 2008
>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?
It runs protocmp. protocmp checks that.
>
>> >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.
I know. protocmp checks that. $ROOT is the proto area. nightly runs
protocmp which compares the proto area to the pkgdefs.
but when you talk about 'unref file checks' that maps to the -f
option and findunref to me.
>
>> 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.
no.
>
>> >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).
no I don't.
I am tired and unwell but still think I'm right :)
>> >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.
nightly catches them.
In fact that's the way I used to create my packages. Do a full build.
Add newthingy. Run nightly (or checkproto if doing it by hand). package
the complaints.
Mike
