Re: Installworld and /usr/include/*.h modification times
On Fri, Jun 1, 2012 at 3:42 PM, Kimmo Paasiala kpaas...@gmail.com wrote: Hello list, 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. If you want, you can do this /after/ a buildworld # mv /usr/include /usr/include.old # cd /usr/src # make hierarchy # make installincludes -- chs, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
On 06/04/2012 00:10, Christer Solskogen wrote: On Fri, Jun 1, 2012 at 3:42 PM, Kimmo Paasiala kpaas...@gmail.com wrote: Hello list, 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. If you want, you can do this /after/ a buildworld # mv /usr/include /usr/include.old # cd /usr/src You don't need to do those last 2 steps below if you mv /usr/include right before you do 'make installworld', FYI. # make hierarchy # make installincludes -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
On Mon, Jun 4, 2012 at 10:12 AM, Doug Barton do...@freebsd.org wrote: You don't need to do those last 2 steps below if you mv /usr/include right before you do 'make installworld', FYI. You are completely right. -- chs, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
On Mon, Jun 4, 2012 at 11:12 AM, Doug Barton do...@freebsd.org wrote: On 06/04/2012 00:10, Christer Solskogen wrote: On Fri, Jun 1, 2012 at 3:42 PM, Kimmo Paasiala kpaas...@gmail.com wrote: Hello list, 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. If you want, you can do this /after/ a buildworld # mv /usr/include /usr/include.old # cd /usr/src You don't need to do those last 2 steps below if you mv /usr/include right before you do 'make installworld', FYI. # make hierarchy # make installincludes -- This .signature sanitized for your protection Thanks! I should have thought of that myself... There are few bits under /usr/share that behave the same way but now I know how to deal with those as well. -Kimmo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
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? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
In message ca+7wwsewnfre8xz3h5huhww78yaxv7dkmyaivzamoy4kuz1...@mail.gmail.com , Kimmo Paasiala writes: 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 =C2=A0when 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 =C2=A0(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? You obviously havn't had to deal with multi-day builds and also having to repair the OS. Preserving timestamps preserves re-startability. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installworld and /usr/include/*.h modification times
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
