Yeah, svn:externals is a working-copy concept that allows you to have your working copy split amongst several SVN destinations (and store that configuration in SVN itself for easy maintenance and reuse). It doesn't help you with local changes to the remote code (in fact, it prevents that arrangement, because changes to the remote code get committed to the remote repository).
You're doing a vendor branch with SVK. The only difference is that you're using SVK to get the code into your SVN repository (in /trunk), rather than using a source drop from the external project (the usual route). There's no difference between the approaches past that step, so you're doing exactly the "recommended" thing. cheers, barneyb On 4/2/07, Zaphod Beeblebrox <[EMAIL PROTECTED]> wrote: > Hmmm...I was thinking svn:externals was more for your working copy. > With SVK, I set up a mirror of Rays svn in my svn (svk calls it a > depot). Then I tell it to sync to my /trunk . Then I tell it to copy > from /trunk to /local. Now, whenever I want to make changes to it, I > check out the local version, I can make all the changes that I want to > and I can also update the trunk version from Ray's. At any point I > can diff or smerge my version and Rays. > -- Barney Boisvert [EMAIL PROTECTED] http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274384 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
