David Summers wrote:
> Hello Subversionistas,
>
> Over the last year or so I've played with a bunch of different ways to
> maintain Subversion RPMs on several different versions of Redhat.
>
> My current server is Redhat Enterprise Linux 3 (actually WhiteBox
> Enterprise Linux 3).
>
> I finally got tired of trying to figure out how to update all dependencies
> of every package involved with building Subversion including BDB, APACHE,
> PHP, Documentation, sub-dependencies, etc., with packages that are
> "updated" from what the original distribution came with.
>
> For RHEL3/WBEL3, today I finally caved and made (some suprisingly simple!)
> changes in my working copy and built trunk and the up-coming 1.1.4 and all
> tests seem to work (I was worried about BDB 4.1.25 but if the tests are to
> be believed, it passed, maybe RedHat fixed the issues with it? I've not
> kept up with Redhat's changes to BDB 4.1.25 but have heard of a lot of
> problems with BDB 4.1.X in the past on these mailing lists).
Yes, people have constant problems with BDB 4.1. None of these problems ever
showed up in subversion tests.
I suggest an alternative change.
Build just db42 and subversion.
Use the system everything-else.
This would use bdb's --with-uniquename support to be independent of the
system BDB, and a small hack to subversion's buildsystem to allow linking to
a BDB which is independent of apr-util.
> For instance, on RHEL3/WBEL3, I've previously been trying to maintain a
> db42-4.2.52 RPM but never liked the problems and options I had for
> installing it, there were always conflicts with existing packages at some
> level of sub-level of dependencies.
Can you go into more detail on this point?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 28 16:16:22 2005