New behavior of subversion's configure: is it good to enforce apache2 with db4 build?!

Hello, users! How are you?

  New versions of subversion FORCE apu-util (and apr, and apache2, if
apr is builded with apache2, not standalone) to be configured with
db4/41/42.

  For which purpose it was done!? All previous versions (0.32.1, for
example) works perfect, when apr know nothing about db4, and
--with-berkeley-db=/path/to/db/libraries/and/headers was passed to
subversion's own `configure'.

  Many (really, many) people don't want to rebuild apache2 with db4
support only for subversion's `configure' script!

  May be it will be rolled back?

--
               Lev Serebryakov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org