Subject: Re: pkg/21700: Subversion requires Apache 2
To: Ben Elliston <bje@wasabisystems.com>
From: Mason Loring Bliss <mason@acheron.middleboro.ma.us>
List: netbsd-bugs
Date: 05/28/2003 00:18:28
On Wed, May 28, 2003 at 01:59:15PM +1000, Ben Elliston wrote:

> I believe that more recent versions of Subversion allow clients to
> connect through an rsh-style pipe like CVS does.  Can anyone else
> confirm?

The following is from the INSTALL file that comes with Subversion 0.23.0.
I haven't actually tested this out yet, but it appears to match what you're
describing. I should shortly be able to confirm whether or not Subversion
works as expected using this method.

---- 8< --------------------------------------------------------------------

  E.  Alternative:  'svnserve' and ra_svn
      -----------------------------------

      As of svn 0.16, we have a new repository-access implementation,
      libsvn_ra_svn (on the client side) and the 'svnserve' process on
      the server.  This is a simple network layer that speaks a custom
      protocol over plain TCP (documented in libsvn_ra_svn/protocol):

         $ svnserve -d     # becomes a background daemon
         $ svn checkout svn://localhost/usr/local/svn/repository

      You can use the "-r" option to svnserve to set a logical root
      for repositories, and the "-R" option to restrict connections to
      read-only access.  ("Read-only" is a logical term here; svnserve
      still needs write access to the database in this mode, but will
      not allow commits or revprop changes.)

      (Expect the server invocation options to change incompatibly
      before they are finalized.)

      For now, svnserve in daemon mode only supports anonymous access.
      But you can also tunnel ra_svn over ssh or any similar tool:

         $ svn checkout svn+ssh://hostname/usr/local/svn/repository

      In this mode of operation, there is no svnserve daemon process;
      the svn client will ssh to the server and run "svnserve -t" to
      do the serving.  Make sure svnserve is in your path on the
      server.  You can override the "ssh" command with the SVN_SSH
      environment variable, or you can define new tunnel schemes in
      the [tunnels] section of ~/.subversion/config.  By default, only
      the "ssh" scheme is allowed.

---- 8< --------------------------------------------------------------------

-- 
Mason Loring Bliss   mason@acheron.middleboro.ma.us   Oderint dum metuant!
https://www.deadsexy.org/    awake ? sleep : random() & 2 ? dream : sleep;