On Wed, Feb 27, 2008 at 12:16:57PM -0800, Mike.Sullivan at sun.com wrote: > >From Nicolas.Williams at sun.com Wed Feb 27 12:11:25 2008 > > >> >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. > > > >But we don't have a file listing unref files, right? Or did I miss it > >when I looked over the nametable? > > There are exception lists in pkgdefs/etc, for things that are placed
Ah, sorry, exceptions, yes. > Note that the pkgdefs exceptions aren't so you can leave random things > there forever because you don't want to delete them from the proto area, > it's for things that need to be there for other components but we can't > ship them (like readline, or wxwidgets). Right. So I could have commands in the makefile to remove cruft we don't want from the proto area and the next person to update SQLite here will get a warning in their nightly log if there's new cruft. I can live with that, but I still need to prevent the two builds (32- and 64-bit) from stepping on each other, and the tmp DESTDIR still works fine for this. Thanks for the explanation of protocmp -- I used to know this.
