Subversion is a version tracking system similar to CVS
Major reasons to move from sourceforge CVS to SVN:
- while most of the firmware has a relatively "free-style" license, copyright of some files (most notably WBO2 code) are restricted, so better be stored off sourceforge
- subversion is technologically better, faster and easier to use
- better authentication and authorization will be applied
Links - since SVN is documented nicely, links are enough for now:
- GenBoard/FirmWare/CVSUsage old CVS repository
- http://subversion.tigris.org/ subversion docs and clients
- install takes 20 seconds in most linux systems, eg. apt-get install subversion command in Debian GNU Linux
- http://tortoisesvn.tigris.org/ a nice windows client, install in 3 minutes to enjoy all features of SVN
VEMS SVN Layout
- https://svn.x-dsl.hu/svn/vems/ VEMS repository. Layout is similar as departments on VemsExecutives:
- hardware
- machining
- ofbiz
- webshop
- chipdocs
- firmware - ignore this directory, see below
- https://svn.x-dsl.hu/svn/firmware/ Firmware repository
- https://svn.x-dsl.hu/svn/manual/ Manual repository (not yet made, still in CVS, see GenBoard/ManualConstruction )
Simple https client (web browser) is enough to view the latest revision (because of nature of SVN, not just head/trunk but of any tags and branches as well). Also useful to find out which subtree you need
However a real SVN client is needed to commit or view history.
Developers ask for SVN access - many haven't asked yet
- jorgen
- humming
- jrussell
- marcell
- pacsa
- grmracer
- phatbob
Please
- use the ofbiz username if possible
- send email to Marcell with your username and
- crypted pw: change pw with passwd command and copy from /etc/shadow ; alternatively use htpasswd command ([windows version of htpasswd]
- or md5sum hashed pw: change pw with smbpasswd command and copy from /etc/samba/smbpasswd ; alternatively use htpasswd -m command
- list of departments you're interested in
- if you need some help with tunneling SVN (only needed for commits; not needed for browsing). You might not know this in advance since "your" proxy might or might not tunnel SVN-https requests properly
- ssh (this was the only supported tunneling to commit through when we used sourceforge CVS)
- httptunnel (might be the best tunnel choice for SVN access. The privacy that ssh provides is not needed when tunneling the safe https through httptunnel)