Andre Ambrosio wrote:
> The "apachectl configtest" gives OK result. And I installed Subversion
> from scratch because when trying to do so with RPMs, there is so much
> dependence and most of them I have older installed which is needed by
> other programs (like glibc). So, I couldn't install via RPM.
>
> If you have any tip to solve RPM installation, it would be the best way
> to get Subversion up and running!
Unless you really want the absolute latest stable Subversion release,
using Dag Wieers' yum repo (see http://dag.wieers.com/home-made/apt/)
instead of David Summers' files should produce a working HTTP-serveable
Subversion install without too many extra dependencies and replacements.
I've been using Dag's packages for some time and I've yet to have
trouble with them - and they don't require replacing anything other than
peripheral stock packages.
I spent a while yesterday trying to build Subversion 1.3.2 with as close
to "stock" RHEL3 (actually the White Box Linux clone) as possible - and
I kept running into failures when I tried to package it.
Direct source build-and-installs seemed to be OK, however. :/
I'll take another quick look at it today - I suspect the problem comes
up with the SWIG bits (Perl and Python bindings), but it's a little hard
to tell.
-kgd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 29 16:42:07 2006