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

Re: Sourcesafe to SVN Conversion Questions

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: 2005-11-03 08:05:04 CET


If you separate the build output (execuables and debugging symbols
etc.) from the source tree, that may make your life simpler:

- use a network file share to distribute/make available these build
products (make sure at least one of the build products indicates what
branch and revision was used to create the build
- developers then use TSVN to *Update* their local copies of the
source tree to whatever revision they need to work on (usually HEAD),
or they *Switch* to the right branch if needed

- if you want to permanently keep copies of the daily builds (which
should not be necessary as all stuff required to reproduce them should
already be versioned), then you could place them in a -- possibly
separate -- repository. Developers could access these builds via a
second working copy pointing to the build-repository (or place it
somewhere in the source working copy using svn:external).
However, as the build products are mostly binaries, each version will
be stored completely in the repo (opposed to just the diff for
text-based files). This will quickly bloat the repository size.




   // \\ @@ "De Chelonian Mobile"
  / \_/ \/._) TortoiseSVN
 <\_/_\_/ / The coolest Interface to (Sub)Version Control
  /_/ \_\ Check out http://tortoisesvn.org

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

Received on Thu Nov 03 07:59:15 2005

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

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