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

Re: storing software releases in Subversion - how?

From: Pep <me_at_there.com>
Date: 2004-08-04 15:44:41 CEST

On Wednesday 04 August 2004 14:24, Ivan-Assen Ivanov wrote:
> 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

It sound likes you need to read the section of the manual on branches.

When you create a branch, the whole trunk is copied in to the new branch.

You can operate on branches just the same as you do on the trunk and the
branch will retain all historic data for all files in the branch up until the
point that they were copied in to the branch.

Also tags help to freeze a branch at a given point in time.

Don't worry about the svn copy command. It really only links the documents in
the branch to the existing trunk versions. They only become files in their
own right when they are separately modified.

Pep.

---------------------------------------------------------------------
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:45:11 2004

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