> I was referring to the case of copying source code which is managed > with e.g. git into a SVN based repository (for example). If you don't > use proper conversion scripts, you will loose the actual history of > the external project (which might be fine if you are using a stable > release). > > I also was not criticizing your setup :-) If it works for you, thats > perfectly fine. My suggestion was to keep your patches in your SVN > repo and to use ExternalProject from CMake (which is quite easy to > use) to clone/patch/configure/build MITK. But this would of course > require a git installation on all your machines. > > Patches which fix the MITK git-dependent build system parts are always > welcome! > > Best, > Sascha
Hello Sascha, no worries :) But yes, we do not use fine granular revisions in the externals, but selected stable revisions. The idea behind that is that we have a stable development fundament for a while, deferring improvements a little. Even if MITK converges really nicely to a stable API for some while now, it really helps if your externals do not suddenly break your own development, especially in a small team like ours. So we pull in / merge the differences from time to time. That was the basic idea. Your second suggestion is also reasonable, but we opted for versioning our patches together with specific mitk/itk/vtk/others externals. So that history is completely in our repository, but not the one of the external projects themselves. Maybe i find a way for the git stuff, till now i am circumventing the internal versioning... Regards, Thomas ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
