On Fri, Jun 01, 2012 at 09:18:55PM +0300, Kimmo Paasiala wrote: > On Fri, Jun 1, 2012 at 8:45 PM, Lowell Gilbert > <freebsd-stable-lo...@be-well.ilk.org> wrote: > > Kimmo Paasiala <kpaas...@gmail.com> writes: > > > >> Why are /usr/include files installed with "install -C" during "make > >> installworld" ??when almost everything else is installed without the -C > >> flag? This makes it harder to track which files were actually > >> installed during the last "make installworld". One can easily find > >> obsolete files ??(that are not covered with make delete-old(-libs)) > >> with "find -x / -type f -mtime +suitable_time" but this doesn't work > >> for /usr/include files because the modification times are not bumped > >> on "make installworld". > > > > "make" uses timestamps to determine whether to trigger a rule. Changing > > timestamps on source files without changing the contents is a bad idea. > > Yes, I'm aware of how make uses timestamps for figuring out out of > date targets. However I would argue that after updating world with > "make installworld" (which is done in single user mode there for > requiring at least one reboot) you should start any compilations from > scratch. The ports system does this by default and cleans up any > previous work files before new compilation. I just don't see where > bumping of mtimes for those files would have that great impact, does > anyone?
With the setting of (vfs.timestamp_precision=1) in sysctl.conf I would have to agree here strongly!. It would be great if this was default especially in any new releases of stable/8 or stable/9. -- - (2^(N-1))
pgp3RKo14DoJR.pgp
Description: PGP signature
