Comments on: Managing third-party software with Subversion http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion Sun, 12 Oct 2008 11:02:20 +0000 http://wordpress.org/?v=2.6.2 By: brian http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion#comment-40693 brian Tue, 23 Oct 2007 17:18:53 +0000 http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion/#comment-40693 Mike's trackback had a good link to the SVN book that talks about "Vendor Branches" as an alternate solution to what I've proposed above. One aspect it discusses that I haven't dealt with yet is making code changes to the 3rd party release and maintaining those changes across revisions. Interesting read at <a href="http://svnbook.red-bean.com/en/1.0/ch07s04.html" rel="nofollow">red-bean.com</a>. Mike’s trackback had a good link to the SVN book that talks about “Vendor Branches” as an alternate solution to what I’ve proposed above. One aspect it discusses that I haven’t dealt with yet is making code changes to the 3rd party release and maintaining those changes across revisions. Interesting read at red-bean.com.

]]> By: Mike Howarth: Web Developer» Blog Archive » Third party SVN imports http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion#comment-40684 Mike Howarth: Web Developer» Blog Archive » Third party SVN imports Tue, 23 Oct 2007 11:50:05 +0000 http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion/#comment-40684 [...] A bit on how people are using svn:externals  [...] [...] A bit on how people are using svn:externals  [...]

]]> By: brian http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion#comment-40293 brian Mon, 15 Oct 2007 17:32:47 +0000 http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion/#comment-40293 @Ryan - Good questions, in looking back at my repo set up, I can see that I left out some details and glossed over an error that I need to fix. You're right - you can't just check out the trunk in the external and then have your core app get that, at least not when deploying. What I left out is that I use <a href="http://andrei.gmxhome.de/filesync/index.html" rel="nofollow">FileSync</a> in Eclipse so whenever I svn update I get my files moved into the right place in my development environment. However, that doesn't cover the deployment scenario and now that I'm looking for my svn:externals for you, they seem to have gone missing. I think I broke something after I got it working so I will sort that out and then get back here to re-document it. In a nutshell though, what you'll want to do for deployment is probably svn export/copy the trunk from the remote repo to a /tags/ directory and make your svn:external reference that. Using the FileSync plugin, you can make your working-copy use the trunk you're tracking remotely but when you're happy with it working the way it is, I think you have to copy it to your tags directory and release against that. Try that and tell me if it works; I'll do the same here. @Ryan - Good questions, in looking back at my repo set up, I can see that I left out some details and glossed over an error that I need to fix. You’re right - you can’t just check out the trunk in the external and then have your core app get that, at least not when deploying.

What I left out is that I use FileSync in Eclipse so whenever I svn update I get my files moved into the right place in my development environment. However, that doesn’t cover the deployment scenario and now that I’m looking for my svn:externals for you, they seem to have gone missing. I think I broke something after I got it working so I will sort that out and then get back here to re-document it.

In a nutshell though, what you’ll want to do for deployment is probably svn export/copy the trunk from the remote repo to a /tags/ directory and make your svn:external reference that.

Using the FileSync plugin, you can make your working-copy use the trunk you’re tracking remotely but when you’re happy with it working the way it is, I think you have to copy it to your tags directory and release against that. Try that and tell me if it works; I’ll do the same here.

]]> By: Ryan http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion#comment-40291 Ryan Mon, 15 Oct 2007 16:01:34 +0000 http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion/#comment-40291 Wow, after reading my comment, I'm not sure that I made any sense. What I'm asking is simply: 1. which directories in SVN are physically created? 2. On which directory are you putting the svn:external property (for transfer specifically)? 3. What is the name of your svn:external property? i.e. "[name] http://svn.riaforge.org/transfer/trunk/" If your setting it up the way your post reads, then you've set an svn:external on repos/externals/transfer to be "trunk http://svn.riaforge.org/transfer/trunk/". Is that correct? If so how can you reference one external from another? i.e. /repo/core/transfer (svn:external to /repo/externals/transfer/trunk) The /repo/externals/transfer/trunk folder doesn't exist in the repository, but would be created on checkout? Any help is appreciated? Wow, after reading my comment, I’m not sure that I made any sense.

What I’m asking is simply:

1. which directories in SVN are physically created?
2. On which directory are you putting the svn:external property (for transfer specifically)?
3. What is the name of your svn:external property? i.e.
“[name] http://svn.riaforge.org/transfer/trunk/”

If your setting it up the way your post reads, then you’ve set an svn:external on repos/externals/transfer to be “trunk http://svn.riaforge.org/transfer/trunk/“. Is that correct?

If so how can you reference one external from another?
i.e. /repo/core/transfer (svn:external to /repo/externals/transfer/trunk)

The /repo/externals/transfer/trunk folder doesn’t exist in the repository, but would be created on checkout?

Any help is appreciated?

]]> By: Ryan http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion#comment-40290 Ryan Mon, 15 Oct 2007 15:34:26 +0000 http://www.ghidinelli.com/2007/10/12/managing-third-party-software-with-subversion/#comment-40290 That looks like a great idea. We're running into the same issues with external libraries (transfer and coldspring oddly enough). I'm having trouble getting the trunk of transfer set up. Do you put the svn:external ref (svn:external to http://svn.riaforge.org/transfer/trunk/ )to trunk on /externals/transfer? Or do you create the trunk folder and put it there? If I do the former, I can't point my core app's /transfer to the svn:external [repos]/externals/transfer/trunk because the the trunk folder only exists when the working copy is checked out. But with the latter way, you'd have to create another directory under trunk in your svn:external definition ("[some_folder] http://svn.riaforge.org/transfer/trunk"). Feel free to email me offline if you're willing to chat about your set up. Thanks for the post. -Ryan That looks like a great idea. We’re running into the same issues with external libraries (transfer and coldspring oddly enough). I’m having trouble getting the trunk of transfer set up.

Do you put the svn:external ref (svn:external to http://svn.riaforge.org/transfer/trunk/ )to trunk on /externals/transfer? Or do you create the trunk folder and put it there?

If I do the former, I can’t point my core app’s /transfer to the svn:external [repos]/externals/transfer/trunk because the the trunk folder only exists when the working copy is checked out.

But with the latter way, you’d have to create another directory under trunk in your svn:external definition (”[some_folder] http://svn.riaforge.org/transfer/trunk“).

Feel free to email me offline if you’re willing to chat about your set up. Thanks for the post.

-Ryan

]]>