Greetings,
I know the subject of why subversion "requires" httpd 2.0.48 and apr
0.9.5 has been beaten to death a couple of times on this list, but I
need to run my particular scenario by the experts as a sanity check.
I am building subversion 1.0.6 on RHEL v.3. For maintenance purposes,
it is not a preferred option for us to install apache via means other
than the RHEL rpms which are kept current via RedHat's up2date utility
and the rhn management utilities. This rules out using David Summers'
rpms or building apache from tarball. The current rpm "version" of
httpd is 2.0.46-32.ent.3, built on 6/28/04. So, it is obviously
patched beyond the 2.0.46 apache releae, and may have some features
backported into it.
Just to see what would happen, I tweaked the configure file to allow
apr 0.9.4 and built subversion against the standard rpm installs of
httpd (with apr) and Berlekey DB (4.1.25-8). The build and
installation went off without a hitch, and initial testing has not
shown any problems. Btw, access is being done via the webdav method,
not via svnserve.
Is there anything that I should be concerned about popping up down the
road with this configuration? Or anything in particular that I should
test before going into production?
Cheers,
-craig
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 9 21:41:41 2004