Re: svn doesn't report modified file when timestamp has not changed

On 2006-07-15 10:17:19 -0700, Justin Erenkrantz wrote:
> Recode doesn't necessarily change the file size either. But, I
> couldn't care less about the fact that recode wants to redefine the
> meaning of mtime: don't use such hacky tools in the first place... --

That's not redefining the meaning of mtime. Even Subversion sets
the mtime to values back in the time (e.g. "svn export"). What is
more important is that it is allowed by POSIX, and POSIX doesn't
say that's bad, and even requires such kind of things for some
commands, like mv. Each tool has its own reasons to change the
mtime value, like "svn export".

And people should stop saying that this will not work with "make"
either. This is wrong. "make" is a different utility and behaves
as expected (using the mtime value as *documented*). And some tools
may change the mtime value just because of "make"; this is the case
of "patch -Z", to prevent some rules from being applied by "make"
after patching the source. At the same time, this can cause problems
with Subversion; for instance, when patching the "configure.in" and
"configure" files, one may want to keep the same mtime value (I had
to do this recently, to make sure the autotools wouldn't be called).

-- 
Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org