Sending to the devel list since more people will likely want this info too ...
On Sun, Dec 28, 2003 at 04:28:47PM -0500, Duncan Findlay wrote: > I'm a little confused as to how to access the new SVN > repository. Someone should probably post some info to -devel > explaining how to access the repository anonymously. Heh. Yeah, it took me a little bit to read the docs and figure out WTF was going on. It's actually pretty easy to convert cvs to svn once you get used to it. The main thing is that instead of CVS pserver or CVS via SSH tunnel, it's SVN via WebDAV/HTTP/HTTPS. They tried keeping some of the CVS UI so people could go from CVS to SVN pretty easily. The first thing I would do is grab the SVN Book (http://svnbook.red-bean.com/) and read at least the intro and such (I skipped the "how to build a svn repo" since I'm not doing that myself ...) To get started, I went to the SVN homepage (http://subversion.tigris.org/) and grabbed the tarball. I then compiled it (./configure --with-ssl), and installed it. Then, to make sure I had the SSL version enabled, I ran: $ svn --version svn, version 0.35.1 (r8050) compiled Dec 24 2003, 22:23:39 Copyright (C) 2000-2003 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ The following repository access (RA) modules are available: * ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol. - handles 'http' schema - handles 'https' schema * ra_svn : Module for accessing a repository using the svn network protocol. - handles 'svn' schema and sure enough, the ra_dav bit does https. Good. At the moment we're in the ASF incubator, so the repo looks like this: $ svn list https://svn.apache.org/repos/test/incubator/sa branches/ tags/ trunk/ if you read the SVN book, it'll explain things, but the short-short version is that "trunk" is HEAD (2.70 right now), "tags" are the same as CVS (one for each version released or thereabouts), and "branches" is the same as well (one for each "stable" release line, b2_6_0 being the latest.) There are 2 things with SVN that matter here. 1) SVN is directory/repo based (for revisions) not file based like CVS. I'm still not quite 100% on this, but basically multiple file changes/additions/deletions are tracked between revisions. 2) tags and branches are really the same thing, except it's expected that no one will be checking in anything new into the tags. So for my dev area, I did: $ svn co https://svn.apache.org/repos/test/incubator/sa/trunk spamassassin-head $ svn co https://svn.apache.org/repos/test/incubator/sa/branches/b2_6_0 spamassassin-2.60 How's that for a short version? As for commit access... I don't recall what's required to get that. Just to get things started, we have me, Quinlan, and JM setup with commit access. I think for anyone else, there has to be a vote of the PMC (same people as above) to allow or disallow. I also don't know if you make the request to us or the ASF folks and they ask us, or ... As we don't tend to give commit access out very often, I'm going to say that only SF CVS commit access folks will be allowed SVN commit access right now. Any other requests can go through this list and we'll go from there. -- Randomly Generated Tagline: Blame San Andreas - its all his fault.
pgp2dNkTEfucg.pgp
Description: PGP signature
