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

Re: RPM Build - Conflict with Redhat 7.2 expat-1.95.1-7

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-10-28 00:41:56 CEST

On Sat, Oct 27, 2001 at 03:10:20PM -0500, David Summers wrote:
> Wow, the list is VERY slow.

The tigris.org machine was down for nearly a full day. Even then, most of
the internet had its old IP, so things weren't working while the machine was
alive (at its new IP).

Last night, I unstuck svn.collab.net's commit emails thru some admin
trickery. It looks like we're up and running smoothly again.

> I've now been rm'ing the expat-lite during my compile/build and using the
> RedHat version of expat and have seen no problems so far. Seems to work
> great.

The expat-lite is simply a subset of Expat, so yes: I'd expect things to
work just fine. The Expat API is stable, so even with a newer Expat, we'd be

> > Trying to build Subversion-r316 with separate neon and apr libraries,
> > everything built fine but when I try to install, there is a conflict
> > between the RedHat 7.{1,2} expat-1.95.1-7 and Subversion's internal
> > expat-lite library. Any quick ideas? Is it time to break out expat into a
> > separate library? Or should there be some subversion build configuration to
> > get rid of the (install-time-only) conflict?

The answer is to pick up a dependency upon APRUTIL. That library figures out
where Expat is, and pulls that into the list of dependent libraries. If
there is no system-installed Expat, then it comes bundled with Expat.

When we add APRUTIL, we drop expat-lite.

[ we also plan to use APRUTIL for some of its DBM features, possibly its
  URI features, and maybe its base64 and SHA1 stuff, too ]


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:46 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.