SVN Unversioned/Non-atomic Commits?

Hello,

I'm in the process of moving a fairly large CVS repository to SVN. We
really like SVN, the atomic commits and ability to move files are an
absolute pleasure for developers.

However, the same atomic commits are causing me a headache. My CVS
auto-building scripts use a small dot-file in the directory for every
project to keep track of when things were last built, versions of
certain libraries on the build machine, and other such metadata.

This was not a problem with CVS, but with SVN, whenever such a file is
checked in (up to 10 times a day), the version of the whole directory
structure gets bumped and real log messages will get somewhat lost in
all the noise.

We considered using non-revisioned tags, but those too are per commit
rather than per-file/directory. Ideally we could make it metadata
pertaining to each projects' directory, or some file within each
directory that does not bump the version of the whole repository.

We have considered doing a one-time check-in of a dot-file, and then
always modifying the unversioned metadata of that single file/revision.
This should work, I think.

Do any experts have any advice?

Thank you!
--Pat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 9 21:04:34 2006