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

Minimal build instructions for svnserver & fsfs only?

From: Matt England <mengland_at_mengland.net>
Date: 2005-09-26 17:22:20 CEST


I have a Subversion 1.2.0-RC1 server running on my Redhat9 system. I run
only svnserve- and fsfs-based capabilities. I want zero
dependencies/interaction with Apache or BerkleyDB; in short, I like my
Subversion running with minimally "dependencies." My current configuration
calls for lots of svn+ssh: client looks (and WebSVN stuff)...and that's
it. Nothing else.

Unfortunately, I forgot to write down my build process to get my 1.2.0-RC1
to build like this. I'm looking to document the procedure.

I am presuming that I can build such a Subversion binary set from a 1.2.3
source tarball without little if any dependencies on Apache, apr, neon,
bdb, dav, or any of the similar stuff outside of the extracted
subversion-1.2.3 directory?

Also, how can I force autogen.sh or configure to make build files that only
allow non-Apache and non-bdb stuff?

Here's the process as I see it right now:

1) extract the tarball
2) cd into subversion-x.y.z
3) sh ./autogen.sh
4) ./configure
5) make
6) make check
7) make install

Prior to executing this, delete any /usr/local/lib/libsvn*
files. Presumably with the "minimal" builds, I won't need to delete
anything else, correct?

The problem with the above procedure for 1.2.3: the ./configure takes
**forever**. This leads me to suspect that there are build processes for
other things (apr, Apache, dav, bdb, whatever) going on __that I
specifically do not want__.

So...I author this email.

Any tips, guidance?

Thanks for any help,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 26 17:25:07 2005

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.