lodewijk@reddwarf.xs4all.nl writes:
> Perry E. Metzger wrote:
>
> > I realize that extracting Apache and such from the process would be
> > very hard, but would it be difficult to make the standard tools able
> > to operate through port forwarded ssh connections the way that CVS
> > happily operates via CVS_RSH=ssh based connections?
>
> on a somewhat related note, using CVS over ssh I can set up a repository on
> machines I only have a lowly shell account on. what is going to be the
> Subversion way of achieving that? right now setting up a server is pretty
> heavy stuff compared to 'cvs init'. will (or can, even) there be something
> like it?
Can you really run 'cvs init' over a network connection? It seems to
hang when kfogel tries that. Can you give an example?
Let me clarify how subversion works:
* to create a repository, you run 'svnadmin create <path>', where
PATH is some local path. It could be right in your home
directory.
* there is [currently] no way to create an svn repository over a
network connection. 'svndadmin create' just writes out a DB
environment.
* when you say "set up" a repository, I assume you mean "make it
accessible over a network". The only way to do that is to use
Apache. Then again, this is no worse than CVS's requirements. If
you don't have some kind of priviledge on the machine, you can no
sooner modify inetd to launch cvs/pserver processes than you can
modify Apache to listen for svn requests.
* if you only want to access your repository locally (via direct DB
access), then compile the ra_local module into your client.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 15 23:49:29 2002