On Tue, 31 Oct 2006, Pete Vickers wrote:
Anybody got subversion running well under OpenBSD with the http/webdav
transport ? It seems to require apache2 amongst a whole shed load of other
dependancies. Google throws up nothing less than 4 years old, so really just
after any experiences to shortcut my legwork.
I have it running on 3.9. Works great. Yes, as a downside subversion
does require apache2 in order to use mod_dav_svn. If you're willing to
forego mod_dav_svn, you can do just svn:// or svn+ssh:// with svnserve
without having to build apache2.
Most of the dependencies (berkeley db, neon, python for make check) can be
added from the packages collection. There really aren't that many
dependencies.
After that, build apache2.
After that, get the subversion 1.4.0 tarball. You won't need the -deps
tarball if you've done everything else right. In my case, I configured
with:
export LDFLAGS=-L/usr/local/lib
export APACHEBIN=/usr/local/apache2/bin
./configure --with-neon=/usr/local --with-apxs=$APACHEBIN/apxs \
--with-apr=$APACHEBIN/apr-1-config \
--with-apr-util=$APACHEBIN/apu-1-config --with-ssl --with-zlib \
--with-berkeley-db
make && make check && make install
Note that if you have previously installed an older version of subversion
you might have to [re]move the existing libsvn* binaries [1] [2].
Also, with 1.4.0 there's a typo in build-outputs.mk (I think). One of the
target man pages is wrong (svnversion.1 should be svnsync.1 or something
like that, search the svn list archives). Easily fixed with a simple
edit.
Then just configure apache2 to use subversion and allow access to your
repositories. Read the apache and svn docs for that.
[1] http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=120899
[2] http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=15509
--
Kyle George
