I have the following situation:
Once in a couple of days we make new "builds" of our software.
A build is a directory tree with files numbering in the 1000s.
Typically only several of them change, several are added, sometimes
several are removed etc.
I would like to keep in Subversion all our builds, so I can
easily access any of them, and take advantage of the diffy storage
to exploit the significant correlation between the contents of
adjacent builds. I have in place a clumsy scheme involving tarballs
and the excellent xdelta utility, but SVN seems a more elegant solution.
So, essentialy, after the build is ready, I must copy it into
a working copy I maintain for this purpose, "svn add" any new files,
"svn remove" any missing files, and commit the whole bunch into the
repository. This would require writing non-trivial tree comparison in my build
script; I'm lazy and would like to avoid doing that. On the other hand,
just "svn remove"-ing everything and "svn add"-ing the new build would
lose the connection between old and new files of the same names, and
thus lose the diffy storage advantage.
Is there a magical combination of commands and switches which will do
what I want?
regards,
Assen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 4 15:24:33 2004