Rockbox Development > Starting Development and Compiling
Subversion version control system information preview?
Mikerman:
If one of the devs has a moment, I wonder if you might briefly explain why the version control system is moving from CVS to Subversion--it would be interesting to hear.
Also, for us non-devs, will there be any apparent ramifications from the switch, apart from (presumably) using a different compiling instruction when compiling/updating the source code?
I assume that info. will be coming at a certain point, but just was curious as a pseudo-techie. Thanks--
dan_a:
There are two big differences between SVN and CVS.
1. In SVN you can rename files and directories, and it understands that they are the same as before they were renamed. CVS saw them as new, separate files so would lose all the history for them.
2. When you do a change that affects a lot of files, CVS sees that as one change for each file, where as SVN sees it as one single change.
There are a number of other differences that may change the way we work in future, but for now I don't think non-developers will see many changes. Oh, SVN seems to be quicker than CVS too, which is always good ;D
GodEater:
I won't make any difference to the command you issue to compile either - that's unchanged.
The only change you'll see is if you're checking the code tree out yourself. Instead of the old CVS command you'll now be doing :
--- Code: ---svn co svn://svn.rockbox.org/rockbox/trunk rockbox
--- End code ---
Mikerman:
And I see that the Simple Guide to Compiling already has the new SVN commands info.--super!
http://www.rockbox.org/twiki/bin/view/Main/SimpleGuideToCompiling
A quick question: if one previously had checked out the source code via CVS and patched it, can one now update the code via SVN and the SVN update command, or does one need to start from scratch with a download of the source code via SVN? Thanks--
Rincewind:
you can checkout the sources from svn to a different directory, then make a diff of your two complete source trees against each other. then you can apply this patch to the svn checkout.
The only problem is, you would need the very last cvs version and the first svn version (so that there are no commits inbetween).
I don't know if this works, I haven't tried it yet with my sources.
I don't think that a svn update directly on your old source works.
Navigation
[0] Message Index
[#] Next page
Go to full version