[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN client vs CVS client

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-12-19 04:48:32 CET

On Dec 18, 2007, at 21:35, Anoop kumar V wrote:

> I am not sure if this is true. But my observation is this:
>
> CVS commandline clients seem more user friendly than SVN
> commandline clients.
>
> In CVS, there is just one file that can be placed in the path and
> executed. There is nothing to install and you do not need
> superuser / root permission to run the client.
>
> In SVN, it seems, you need to go through installation - the
> binaries are rarely available - it took a long time to find one for
> Solaris. And the instructions said that I need to be root to
> install and use the client.
>
> I am not complaining here - I am only trying to understand if the
> above is true. And how does one go about using an svn client (not a
> server) from solaris commandline. I cannot install anything, just
> want to connect & checkout code kept on an SVN server.
>
> Is this easily possible?

Binaries are available for many platforms. You will probably need to
be root to install these, though.

You definitely do not need to be root to use Subversion. You will
probably need to be root to install Subversion to a system prefix.
You can instead configure Subversion in another prefix to which your
user has write access and build there instead. And you don't need
root for that. Subversion has many library dependencies. If those
libraries are not already on your system, you would need to build and
install those, perhaps also in a different location than normally.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 19 04:49:01 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.