[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: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-11-03 00:44:13 CET

Scott Prugh wrote:
> Forgive us, but we are a Sourcesafe shop and trying to convert to
> Subversion. I'm running into some mismatches with how SS does stuff and
> how SVN does it. I'm trying to fit SVN into our process but struggling
> with some of the constructs. Any advice you can give would be helpful.
> We build some 300+ executables every night and push out this build to
> centralize servers so that developers can grab the latest integrated
> build and start working.
> Today in Sourcesafe, I simply grab the build and set my working
> directory and you are set to checkout.
> This doesn't really seem to work with SVN/TSVN. The only way I can seem
> to get TSVN to recognize a folder is to do a checkout. This will only
> work if the directory is empty. So, I would have to check out
> everything, and rebuild to start working. The rebuild takes 6 hours, so
> this is not possible.
> If I do chekouts at the leaf folders, this seems to work, but I need
> global properties set from the root for all developers like
> bugtraq:message. So, here are the questions:
> -Set Working Folder
> Is there a way to swap in a delivered build so that TSVN recognizes the
> binding to the URL in subversion? Perhaps if I do a checkout on the
> build machine and deliver that whole directory? Any other way?
> -Get Latest?
> Is there a GetLatest equivalent, or do I have to start with a clean
> directory each time? In other words, I can't seem to get files from SVN
> unless the target directory is completely empty. I get an error
> otherwise.
> -Global Properties
> What is the best way to set global properties like bugtraq:message and
> others? When I put them in the config file they do not seem to take
> effect. When I put them in the root of a repos branch they do not
> propogate to child folders. This may be because I am just getting the
> leaf and not all folders in between.

I am struggling a little with your terminology, but it seems you have
not grasped the basics of subversion yet, and the difference in terms
from VSS.

When VSS refers to checkout it means getting an exclusive lock so you
can start editing. When SVN refers to checkout it means pulling down a
working copy from the server. You only do that once, and you keep the
working copy until the project dies, or you stop working on it.

To get the latest from the server you need to 'Update' your working
copy. That will pull down just the changes from the server, so the WC is
synchronised with the server.

You *really* should read the subversion manual, or at least the
TortoiseSVN manual to get a handle on how it works.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.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:06 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.