Glenn E. Sieb wrote:
> Michael Mason said the following on 11/30/04 12:26:
>
>> The problem is that you're trying to check out different repositories
>> into
>> the same directory, . in this case. Subversion won't let you do that,
>> because after the first checkout is done, . is a working copy.
>>
>>
> *nod* makes sense--will get me lots of pushback tho :-/
>
>> This would work (you don't need 'HEAD' - Subversion gets the latest code
>> by default)
>>
>>
> *nod* they're being anal about it.
>
>> $ svn co svn+ssh://reposerver/svn/One/trunk/ workingCopyOne
>> $ svn co svn+ssh://reposerver/svn/Two/trunk/ workingCopyTwo
>> $ svn co svn+ssh://reposerver/svn/Three/trunk/ workingCopyThree
>>
>> Now this still probably doesn't achieve what you want, since you'll have
>> three directories on the client. What might work better is to create a
>> new
>> project in your repository which pulls in items from the other
>> repositories using svn:externals. There's more in the book here:
>>
>> http://svnbook.red-bean.com/en/1.0/ch07s03.html
>>
>>
> Thanks--I'll check into that.
>
>> Another thing you might consider is using just one repository - why do
>> you
>> feel you need three separate repositories?
>>
>>
> It's called office politics. :) Three different groups work on three
> sections of the code. You know how that is.
If you use apache to access repos (always recommended in multi-user env,
I would say) you can set path based access control directives achieving
exactly the same result.
Guido
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 09:14:09 2004