[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Can time stamp changes force a commit operation?

From: Pedro Sanchez <psanchez_at_nortelnetworks.com>
Date: 2004-04-16 20:47:28 CEST


Is it possible to tell subversion that a change in the time stamp of a
file is enough to get it into the repository with the next check in
operation? that is, even if the content of the file has not changed?

Alternatively, is it possible to force a change in the time stamp of a
file stored in the repository?

If you are interested in why I need this please read below.


My need for this arises from the following: I have project, a GNU Make
system, in my subversion repository with two main files, A and B, and a
bunch of other secondary files. There are two users of all these files,
end users, and the maintainer of the project, me.
End users of my project simply get all the project files and use them to
generate their *own* stuff. The files in my project should never be
touched by the end users.
On the other hand, during development of the GNU Make system, the
project maintainer may need to run a process P that recreates files A
and B, and several secondary files. However, only under corner
circumstances file B actually changes, most of the time this file just
gets a new time stamp equal to that of file A. When it comes time to
check in the changes, file B is not committed because its content hasn't
The problem is, when the new version of the project is distributed to
the end users, file B shows up being older than file A, forcing the GNU
Make system to try to rebuild the whole thing. Since end users usually
don't have all the tools, or the right version of the tools, to
successfully rebuild the project the system fails.
More specifically, A=configure, B=aclocal.m4 and the project is a GNU
autoconf/automake project. Process P is the bootstrap script. So I run
P, which recreates configure and aclocal.m4. When I check in the
changes, configure goes in, and I want aclocal.m4's time stamp to be
updated in the repository as well. Otherwise it is going to become older
than the new configure, and that breaks the system. If aclocal.m4 is
older than configure the autoconf/automake thing will automatically kick
in an attempt to rebuild the system.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 16 20:47:58 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.