Re: [Swig-devel] Change to subversion?

[William S F. <ws...@fu...>]

John Lenz wrote:
> On 11/13/06 18:16, William S Fulton wrote:
>> *** ANNOUNCE: SWIG 1.3.30 (November 13, 2006) ***
> 
> Now that 1.3.30 is released, I think this would be a great time to
> migrate to subversion.  We mentioned this earlier on the list, but we
> were all focused on the release.  The advantages to subversion over cvs
> are too many to list here, and other articles cover it better...  svn
> status, client side svn diff (no network activity), directory wide
> revisions (so  the set of changes to all files changed with a single
> commit are kept together), svn move, svn switch, and so on....
> 
> http://subversion.tigris.org/
> http://www.onlamp.com/pub/a/onlamp/2004/08/19/subversiontips.html
> http://osdir.com/Article203.phtml
> 
> Subversion has excellent documentation
> http://svnbook.red-bean.com/
> and even has a section "Subversion for CVS Users"
> http://svnbook.red-bean.com/nightly/en/svn.forcvs.html
> 
> The conversion process at sourceforge is for someone (I volunteer) to
> download the CVS archive (using rsync to get all the files) and run
> cvs2svn script.  (The cvs2svn script is a python script that uses the
> SWIG wrappers of the subversion libraries!)  The cvs2svn output is then
> uploaded to sourceforge.
> 
> http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1
> 
> When we do decide to switch, everyone will have to not commit anything
> for a day or so.
> 

I'm all for converting to subversion if someone wants to go through the
process. So John, I'm fine with this as you've volunteered. If you need
any more SF permissions to achieve this let me know. Would you mind
updating the cvs web page with new instructions when done?

One thing though, there is a php branch at the moment. Will this appear
in the svn repository too? Will the new repository keep all the history
from the cvs repository btw?

In one the links above, it mentions that subversion supports a mode
where it will automatically convert line endings to whatever system you
are on. Either we do that or keep to the current approach and use unix
LF only. This latter approach is a bit frustrating as most windows
editors will not respect the type of line endings, including visual
studio which is the main editing tool for some. I'm not sure how
tolerant cygwin make is of DOS CR/LF though. That must work as it is the
main Windows environment for developing, so we will need to test this.
Maybe we get Unix LF when using Cygwin svn, which might mean we can't
mix a Windows GUI svn client with the cygwin commandline svn. Probably
it will all 'just work', well, maybe.

William