That's exactly what I want and not that I don't mind but I like it better
that I have to check in the changes of the externals folder separately; it
keeps things clean. Provided one remembers to check them in. Thanks for
everything.
----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: Fri, 18 Aug 2006 01:58:01 +0200
On Aug 17, 2006, at 23:35, 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 repo
>>>
>>>ProjA
>>>ProjB
>>>ProjC
>>>ProjD (just a common library folder w/o branches & tags & trunk
>>>subfolders)
>>>
>>>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"
>
>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.
Using the command-line client, if you make changes in your project proper,
and also within the "libs" directory pulled in via external, and you commit
the root of the working copy, only the changes to the project proper will
be committed; the changes in the libs directory will not be committed. You
can commit them separately by changing to that directory and committing,
and they will be committed back to $REPO/ProjD where that directory comes
from. This also means that any other project using $REPO/ProjD via external
will automatically inherit these changes, which should be what you want. If
that isn't what you want, then externals may not be the right solution for
this task.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 18 05:05:21 2006