Take a look at piston (http://piston.rubyforge.org/) , as it was designed specifically for this purpose.
How it works is you keep the svn:externals and use piston to lock the svn:external at your chosen external revision. The lock revisions are svn:props so they are versioned along with erlyweb, so when you checkout any version of erlyweb, you get the correct externals for that version. Another side benefit of piston is that you get a complete checkout even if one or more externals are temporarily unavailable. This would matter greatly if you use 3rd party externals. Only the server needs to 'gem install piston', not the clients, so from the clients (our) perspective nothing has changed, but now we automatically get correct and tested versions of externals for any given version of erlyweb. Clients could install piston and manually update their externals, and it is nice that it is possible but is not required to get the benefit of piston. A 'pistonized' subversion repository would be tranparent and fully compatible with Git mirroring. Also, Git as of v1.5.3 added support for sub-modules (externals), so now I have no reason to use Subversion. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
