RE: A simple build script question

>> Then I get an error during the build that the 'script' folder already
>> exists:

>I've never seen that when attepting to co ontop of an existing working
copy.

You are correct that you can "co" on top of an existing working copy,
but that's not what I was doing. (Although it is what I *wanted* to do!)

Here's the command again:

        svn co svn://machine:port/project/trunk/script c:\project\script

This doesn't checkout the script folder, it checks out children of the
script folder. In other words, the c:\project folder does not contain a
.svn folder so if you try to checkout "[base url]/project/trunk" onto
"c:\project" after the above command it will complain because the
"script" folder already exists as a non-working copy (for lack of a
better term)

> My script does what I think you already do. If I just wanted to check
> out the doc directory I would run:
>
> svn co svn://d43706v6/Proj1/trunk/doc C:\tmp\doc.

I agree, but then if you tried to do a checkout of Proj1/trunk to C:\tmp
I think you would get the same error I got.

As I mentioned to another poster I'm leaning towards changing the
release process. Instead of a pre-build that only checks out the script
folder, I will have the pre-build checkout the entire project folder.
The other change will be to remove the delete/update from the build
process since it is not necessary if the pre-build gets a fresh copy
from the repository.

-mk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 11 22:57:08 2006