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

Re: SVN Externals

From: Res Pons <pons32_at_hotmail.com>
Date: 2006-08-17 23:35:45 CEST

Very clear. I just ran your command and replaced the paths and it worked.
Now, here's a question I have: Whatever I do in this newly created symlinked
folder...does svn treat it as if I was directly in the folder or inside the
source project? Thanks your example was very clear.

----Original Message Follows----
From: Ryan Schmidt <subversion-2006c@ryandesign.com>
To: Res Pons <pons32@hotmail.com>
CC: markp@softlanding.com, users@subversion.tigris.org
Subject: Re: SVN Externals
Date: Thu, 17 Aug 2006 22:20:42 +0200

On Aug 17, 2006, at 21:59, Res Pons wrote:

>Thanks for all the info. So if I'm running svn on a linux redhat
>enterprise 3.5 server and I have the following projects at the root of the
>ProjD (just a common library folder w/o branches & tags & trunk
>And I want projD to be symlinked into A, B, & C when everyone checks out
>these 3 latter projects so they automatically get projD into their working
>folders... say I go to ProjA and create a file called what and what I do
>put in it and just check it in? Our SVN server is a Linux box and
>developers either use Eclipse plugin or svn commnad line; the Tortoise
>example totally lost me. Sorry.

If $REPO is the URL to your repository, then:

cd /working/copy/of/ProjA/trunk
svn propset svn:externals "libs $REPO/ProjD" .
svn ci -m "Adding external to bring $REPO/ProjD into this project into a
directory called libs"

It's explained in the book:


Express yourself instantly with MSN Messenger! Download today - it's FREE!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 17 23:37:11 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.