On Fri, Jun 04, 2010 at 10:31:22PM -0700, patrick keshishian wrote:
> On Fri, Jun 4, 2010 at 7:49 PM, Jacob Meuser <jake...@sdf.lonestar.org>
> wrote:
> > I'm still curious how anything left in /usr/obj can be anything
> > but a possible problem after updating system binaries and sources
> > to a new release. especially for people who are just "following
> > the directions as they are written."
>
> Do you not agree barring broken makefiles and unreliable system clock
> (as someone pointed out), object files and binaries (in obj/) should
> have been rebuilt?
>
> --patrick
Consider the follwoing scenario:
I have a release n system, last built on May 1. So the obj files have
a time stamp of May 1.
The files of the tarbal of the new release n+1 have timestamps of Apr
1 or earlier, since it was made at that time.
If I then install the tarball by extracting, according to makethe
object files are still fresh, since the sources will be older than the
object files. By default the files extracted form a tartball get the
timestamps from the tarbal.
There are some variations on this scenario.
-Otto
