There is no support for arbitrary db versions, the 1.3.2 version only arrives to support db 4.6, otherwise it fails to find it. The problem is that, since it does not have any specific dependency about it, the new portage now breaks --depclean when the (masked) 4.7 version is installed because of this: * sys-libs/db-4.6.21_p1 pulled in by: * dev-libs/apr-util-1.3.2 * dev-util/subversion-1.5.1 I _think_ subversion inherits it from apr-util. Not nice...
(In reply to comment #0) > the 1.3.2 version only arrives to support db 4.6 It isn't good to mix stable APR-Util with unstable Berkeley DB, but you can find the patch here: https://svn.apache.org/viewvc?view=rev&revision=671382 https://svn.apache.org/viewvc?view=rev&revision=671383 > The problem is that, since it does not have any specific dependency about > it, the new portage now breaks --depclean when the (masked) 4.7 version is > installed because of this: > > * sys-libs/db-4.6.21_p1 pulled in by: > * dev-libs/apr-util-1.3.2 > * dev-util/subversion-1.5.1 > > I _think_ subversion inherits it from apr-util. Subversion built with USE="berkdb" directly uses Berkeley DB. Subversion's build system on Unix-like systems always chooses this version of Berkeley DB which is used by APR-Util.
fixed in 1.3.4
