Norm Jacobs wrote: > Without setting timestamps consistently across installations, tools that > compare timestamps to determine what to do don't work at intended. For > example, make(1). On a single installed environment, this generally > isn't a problem. When you want to distribute work across machines and/or > use zones, the inconsistent timestamps can be a problem.
Could you give a more specific example? It seems to me that if a file changes on a machine, any target would immediately be out of date with respect to that file, regardless of its timestamp, and so you'd want the timestamp to reflect that -- have the current time. It seems sketchy to compare timestamps on individual files across systems, anyway. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
