In order for Apache 2.0.44 to support Subversion, Apache must be compiled with the "--with-dbm=db4" configure flag, assuming BerkeleyDB 4.0.14 or greater is already installed. If there were a USE flag such as "db4" that could be used to specify which BDB version to use when compiling Apache to support Subversion, then the build could be the same for everyone else who doesn't need db4 support in Apache. Reproducible: Always Steps to Reproduce: 1. Merge Apache 2.0.44 2. Merge Subversion 0.18.1 (see bug 17308 for ebuild script) 3. Create svn repository and configure Apache to publish it (/svn/repos example) 4. Navigate to http://localhost/svn/repos to view BDB error I don't want USE flags to get out of control, but if that's the only way to customize the flags given to the "./configure" script, then that's the way the system works.
i had the same problem - emerged berkeleyDB >=4.0.14 manually and then 'emerge apache' - having apache2 enabled in the use flags - the newest version of apache2 was reemerged (with yacc as a new required package) - now subversion (i used the 0.19 ebuild from bugs.gentoo.org) works without problems... it seems that the apache2 ebuild uses the highest available version of berkdb by default - maybe the use flag is not necessary
nope, its not.
