Hi,
> > While I don't want to hold up 1.0.1, httpd is planning on 2.0.49 for
> > this Wednesday. Sander should be laying the tag first thing Monday
> > morning. I know there are some fixes in apr and apr-util that you guys
> > want - all of those should be rolled into there. *shrug* -- justin
>
> Oooh ooh ooh.... that's great news. It means that the 2.0.49 apr-util
> will actually know how to detect db4.2 for real.
>
> We could release 1.0.1 first, and then a couple of days later tell
> people to upgrade to apache 2.0.49... but not everybody builds apache
> either. Maybe it's worth waiting a couple of days so that our 1.0.1
> tarball can get a copy of the 2.0.49's apr-util. The db4.2 problem is
> huge in my mind.
Well, I think shipping the new APR with Subversion for those who build from
source, is a good idea because I too believe the BDB 4.2 detection is a huge
problem. Stating it as a requirement isn't such a good idea since having a
working version of APR which comes with Apache 2.0.48 will suffice. It could
stop people from upgrading, which would be unnecesary. We already require APR
in Apache 2.0.48 which is more strict than required by Subversion itself. When
not building mod_dav_* one only needs APR 0.9.4 (except for configure
preventing this).
I found that people did not want to upgrade when we started requiring BDB
4.2.52 - when actually this requirement was meant as an advice.... - and
Subverison - even now - works well with 4.0.14.
bye,
Erik.
--
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 7 19:40:05 2004