RFC: set timestamps on files created by bzr

[Martin Pool]

On 22/01/2008, Robert Collins <robertc at robertcollins.net> wrote:

> If bzr were to set a timestamp on any files it alters that is the same
> for all files altered during the same operation, then timestamp-based
> build systems that have these issues would not trigger rebuilds
> incorrectly allowing wide scale deployment.

So they'd all be set, say, to the time we started doing the change?

It's an interesting point.  I can't think of any problems with doing
it.  Would you just have it always turned on?

> This could be done by calling futime (which is not exposed in python
> AFAICT, we'd need an extension to make it available) during writing the
> files in tree transform.

Why isn't os.utime enough?

-- 
Martin