>> BTW, (and sorry if the question has been asked before) why doesn't the >> repository moved to a SVN/GIT one? I've been working under CVS before SVN, >> but I never came back! ;) > > This is how I explained it a while ago: > > http://daniel.haxx.se/blog/2008/04/14/why-curl-sticks-with-cvs/
Hi Daniel, I don't want to seem impolite, but in my humble opinion, some (not all!) of your arguments may be nuanced. Here is what I think: - CVS is good enough: agreed, even if I prefer SVN - CVS is rock solid: yes, but in 2009 I think we can say SVN is rock solid too. - Integrated with automated build system: I don't know... maybe SVN could do it too, but I'm unaware of the build system. However, if we manage to have a CMake build system, then we could easily have unit-tests and nightly/hourly automated builds with automatic reports (CTest/CDash). Is that you have? - Cross-platform problems: I'm not a specialist, but I though SVN works on all platforms CVS does. Am I right? My arguments in favor of SVN are: - switching from CVS is very easy - SVN+CMake+CDash may be a candidate tool chain Conclusion: Why changing something that already works? Well... I think switching may be possible in the future, but not right now. Well... in my opinion! Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
