I wrote: >> >> I understand what the topic is. I don't understand your comment, "I'd >> be inclined just to remove all files in those directories which are older >> than some file in the build tree--*after* a successful >> installation." > > Ah, sorry, that might bear more explanation. > > > "install -C" doesn't change the timestamp, so you'll have tons of > > files that are older than "some file in the build tree". > > What does the last access timestamp look like after install -C?
I'm not sure at this point in time (I haven't looked at the source in a year or so). I know "install -C" preserves the last modified and probably the created time. > > > You don't blindly want to remove files and I doubt you want > > mergemaster to list possibly hundreds of files as removal > > candidates. So, yes, "install -C" confuses the issue :-) > > Indeed. What good reason do we have to use it on these directories? On slow hardware, "install -C" can significantly speed up a "make installworld", because the installworld doesn't have to copy any files from /usr/obj to some destination. I'm beginning to think a mtree.obselete is the way to go. Each committer, who deletes something from the base system, should be required to update mtree.obselete. I think we should also add a "make purifyworld" or a new mergemaster option should invoke the mtree.obselete to clean the tree. I normally use touch(1) and find(1) to eliminate cruft. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message