Scripsit Russell Coker <[EMAIL PROTECTED]> > Incidentally I wrote a shared object to support changing the apparent time > which was actually useful for such tasks as Y2K testing and running demo > software. Getting it to change the time() library call was easy, changing > the time stamp on files that were written was more painful.
Hm, perhaps such a thing could also be useful for testing properties such as "source packages A and B build bitwise-identical binary packages on architecture X" which would otherwise be skewed by timestamps embedded in the files in the binary packages. This might be useful post-Vancouver for letting lesser architectures sneak #ifdef'ed corrections into the stable source pool without risking functional changes on the released architectures. -- Henning Makholm "De spiller på harpe og drikker øl."
