[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: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2005-11-03 17:28:32 CET

Scott Prugh wrote:
> So, it goes like this:
> -Build machine gets current from SCM
> -Build is executed and made available
> -Developer grabs build
> -Developer points SCM to root of build
> -Developer starts checking out files
> So, I think we have two options:
> 1) What you suggested. Write a script that would pull down all current
> binaries/debug symbols, etc from a current build. Have the developer do
> the chekout once. This is interesting. I never thought of it that way.

IMO, this is a much saner :) approach. If a developer is working on
something they can continue working on it. They don't have to try and
copy their changes into the "new build". The new build binaries get
plunked into their semi-permanent working copy. If you make your build
from a specific revision then you can just include that information in
the build so if developer wants their source to match exactly what
created the build they can simply "update to revision" while still
keeping any modifications they're working on.

> 2) Take the build with all the .svn directories. Will this work? Not
> sure. I'm trying it right now.

I suppose it could work, assuming everyone is on the same platform
(think windows CR/LF vs. linux LF), but again, IMO it is much easier
for a developer to have a permanent working copy where they can make
their changes and the build output is the transient thing that they can
refresh if they want.

But as someone else suggested, making your system work so you can have
separate trees for build output and source would be even better.


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

Received on Thu Nov 03 16:29:09 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.