Hi all,
some time has passed since the last poll, so I'd like to know if
anyone has changed idea about this.
To summarize:
1) I can grant SVN is easy to learn specially for those who use CVS.
Basically all you need to know (at least for basic usage) is:
a) unlike CVS it uses a single number for revisions (e.g. CVS: 1.324
SVN: 324). This makes a lot of sense once you get used it !
b) HEAD is TRUNK in SVN terminology
Reading first paragraphs of the "Subversion for CVS Users" doc at
http://svnbook.red-bean.com/en/1.0/apa.html
will be enough to be able to do practically everything you did in CVS in
the new SVN world!
2) GUI tools for SVN are available for both win and Unix even if on Unix
I always use command-line tools (just like I use commandline tools also
for CVS).
3) HD usage of SVN will be more than CVS. I did almost all steps (not
the final one!) for importing CVS contents of wxCode into a new wxCode
SVN repo and found that wxCode CVS repository is around 108 Megabytes
currently. The "svn dump" I obtained for upload in SVN repo is around
240 Megabytes. I'm not sure however if this means that a SVN checkout
will take the same amount of space... (I strongly doubt - since 240 MB
is the repo with all revision history; a checkout only contains last
revision).
4) if we enable SVN for wxCode, we do not need to turn off CVS. The two
can coexist. In fact, I think we will never be able to satisfy all
maintainers if we choose X over Y. Thus I think we should have both CVS
and SVN repositories, *without* component duplication: a component is
either in the CVS or in SVN, not in both.
I know that many of you noted that this makes it harder to have all
components of wxCode in a single place. However this problem could be
solved creating a simple script (for Unix at least) which check-out all
CVS repository and SVN repository and "merge" them in the local harddisk
of the user. This can be obtained just doing:
a) cd $folder_where_we_must_checkout
b) cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/wxcode checkout wxCode
c) svn co
https://svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components
wxCode/components
in that way user will get a wxCode/components folder containing both
components under CVS and components under SVN.
5) SVN is
a)somewhat faster
b) allows to do practically everything offline (eg see which files
have been modified and how), including removing folders added by error
c) SVN supports attributes and permissions; this means that e.g. a
Windows developer can set the executable flag on the "configure" script
of its component without changing to Unix workstation. I'm sure this
will greatly help people which develop from Windows components
supporting also Unix.
6) last time there were:
3 pro: me, Angelo and Cecilio
2 against: John, Otto
2 undecided: Ulrich, Joseph
Anyone changed his mind ?
:D
Francesco
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
wxCode-users mailing list
wxCode-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxcode-users
