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

Re: Solaris SPARC :: Client only for subversion ??

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-29 03:04:23 CEST

On Aug 29, 2006, at 01:59, Greg Morse wrote:

>>> I have subversion package installed and running on an UBUNTU linux
>>> box.
>>> I would like to get clients that I can install on various SPARC
>>> Solaris 8 boxes to connect to and use the UBUNTU server.
>>> Is there a 'client only' (i.e. just svn, not svnadmin) version of
>>> the
>>> package whose install is more simple than the server version with
>>> all
>>> its prerequisites?
>>> (Same question for winXP client).
>> No; the client has the same prerequisites as the server so there
>> would be no point.
> Thanks for the reply Ryan.
> This does seem very counterintuitive.
> When I look at the list of dependencies required to get Subversion
> to run on Solaris, it is quite extensive.
> Apache2.0.59, ssl, swig, gcc, libiconv, libxml, db4.2, gdbm, .....

As far as I know:

Apache is only required if you've told it to build the Apache module.
If you're just going to use this as a client, do not tell the
Subversion configure script to build the module, and Apache will not
be required.

Neon is required by the Subversion client to be able to connect to a
repository served over HTTP. Perhaps you can omit this if you do not
want to access repositories via HTTP.

OpenSSL is required by Neon to allow connections over HTTPS. You can
omit this if you don't plan to access repositories over HTTPS.

Swig is needed to build the various language bindings. If you don't
plan on writing software (a Java program maybe, or a Python script)
that interacts natively with a Subversion repository, I'd guess you
can skip this.

Gcc is the compiler, which you obviously need to compile anything.

Iconv is for internationalization and text conversion. Yes, the
client needs to do this just as much as the server.

BerkeleyDB (db4.2) is not required; you can omit it from the build
process, and you will then only have direct filesystem access to FSFS
repositories, and not BDB repositories. (Remote BDB repositories
accessed over http, https, svn or svn+ssh protocols would still be
available.) I personally configure without BDB support because I
don't need or want it.

I don't know what gdbm is.

> Plus warnings about backing up my existing apache server config
> before installing the new one. (which may not be newer in fact......)
> It seems like a lot of risk, and a lot of overhead just to run an
> subversion 'client'.
> I could see it if I wanted to run the server, but for a client
> only, I was hoping for something lightweight.
> Anyway, it is what it is, and thanks for the answer.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 29 03:05:54 2006

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.