Developing bleeding edge. Dealing with multiple svn repos?
Posted: Thu Mar 01, 2007 4:58 am
What's the best way to handle bleeding edge development, where you not only run your own project from subversion, but you also depend upon other libraries from third-party svn repositories, which you want to add to your own repository but update from the third-party repository?
So you might have this:
The only way I can see to use that third part package is to check it out of the third party repository, then copy it into my repository and "svn add" it. Updating from their svn repository becomes long-winded where I need to get rid of it from my repository, update the checked out version I have elsewhere on disk and then copy it into my repository again and re-add it. Surely there has to be a better way to use other people's repositories inside your own svn repos? 
It's be cool if with /repos/trunk I could run "svn update" and it updates my own files, and also any changes that were made in the third party repository.
So you might have this:
Code: Select all
/repos/branches/
/repos/tags/
/repos/trunk/
/repos/trunk/lib/
/repos/trunk/lib/YourClass.php
/repos/trunk/lib/YourPackage/
/repos/trunk/lib/YourPackage/SomeClass.php
/repos/trunk/lib/CoolThing/ <----- From a third party!It's be cool if with /repos/trunk I could run "svn update" and it updates my own files, and also any changes that were made in the third party repository.