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

Re: Checkout from multiple reps

From: Mness <mness_at_one.net>
Date: 2003-02-28 21:08:44 CET

If my repository looks like so:

Trunk
|-CopyProj
| |-Bin (copy.exe)
| |-Copy (copy.cpp)
|
|-PasteProj
| |-Bin (paste.exe)
| |-Paste (paste.cpp)
|
|-CPWorkspace

And 'svn propget svn:externals CPWorkspace' shows:
test file:///C:/backup/svn/trunk/CopyProj
test file:///C:/backup/svn/trunk/PasteProj
only the second line is executed.

If it looks like:
. file:///C:/backup/svn/trunk/CopyProj
. file:///C:/backup/svn/trunk/PasteProj
I get the obstructed update error stating that URL ... does not
match existing URL. I am sure only the second line is still
being executed as well (the conflict is with CPWorkspace and
PasteProj).

My goal is to get:

CPWorkspace
|-Bin (copy.exe paste.exe)
|
|-Copy (copy.cpp)
|
|-Paste (paste.cpp)

as my working tree. Are these the 'some bugs' that you mentioned,
or am I not getting it? If this is just something that should never
work, I guess I could put every binary file in the same directory in
the repository, but then how do I indicate that only some of those
files are supposed to be checked out in a svn:externals dep (i.e.
if I also had a 'Cut' project that should not be in the CPWorkspace)?

Thanks for the help. Regardless of the turnout of this issue, I am
switching my personal code over to Subversion. Really like the
changes in philosophy that you made with SVN.

--
MNess
---------  Original message --------
From: Karl Fogel <kfogel@newton.ch.collab.net>
To: Mness <mness@one.net>
CC: dev@subversion.tigris.org
Subject: Re: Checkout from multiple reps
Date: 02-28-03 10:46 AM
> &quot;Mness&quot; &lt;on.mness@nuvox.net&gt; writes:
&gt; Does anyone have suggestions of how to do this cleanly?  My first
thought
&gt; was to just checkout many projects at the same level (or use the
ext-dep
&gt; property to build a module) and let each project add it's files to the
bin
&gt; dir.  It seems that this feature was excluded on purpose though (from
&gt; reading the bug log).
The svn:externals property is the way to go, as you guessed.  It's not
excluded, but does have some bugs, which will be fixed before 1.0.
That's the most we can offer you, I think :-).
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 28 21:09:44 2003

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