1
other / [wishlist] Make CS an external definition in PS SVN
« on: August 01, 2008, 06:10:17 am »
Apparently each revision of planeshift is firmly tied to a specific revision of crystalspace. I think maintenance could be greatly simplified by using revisioned external definitions. That way developers and testers could automagically pull the correct CS version without having to bother about revision numbers themselves. It also has some other nice benefits, please read http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html for details.
example "patch":
example "patch":
Code: [Select]
Property changes on: trunk
___________________________________________________________________
Name: svn:externals
+ crystalscpace -r30564 https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk
this will pull CS rev 30564 into trunk/crystalspace when you co/up trunk. You can use svn:propedit to change this to a different version in your working copy, and when you check in everyone pulling trunk will update to the changed revision as well (unless they also changed svn:externals, in which case they will have to resolve the conflict first, just like with a regular file). When you later use svn merge or svn copy to make/update a stable branch, the svn:externals property will be preserved just like a regular file, so users pulling the stable branch will always pull the correct revision of CS, regardless of what you do in trunk.