When emerging subversion without Berkley DB support (USE='-berkdb') sys-libs/db is not a dependency, which causes subversion to fail with the following error: /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/../../../../i686-pc-linux-gnu/bin/ld: cannot find -ldb-4.2 subversion version in question is: dev-util/subversion-1.3.0 USE="bash-completion java nls perl python zlib -apache2 -berkdb -emacs -nowebdav -ruby"
Re-emerge apr and apr-util... *** This bug has been marked as a duplicate of 114481 ***
The consistency of my packages is fairly well, apr-utils has already been compiled without berkdb. Now, it is possible apr wasn't compiled after apr-util had been recompiled, but this would mean there is a way to defeat the dependency system. Is there a clean way to protect oneself against this? ea. emerge apr apr-util with +berkdb toggle to -berkdb emerge -uvDN world will remerge apr-util with -berkdb apr will not be updated, so I'm guessing this is what causes subversion to be forced to link against berkdb. What can be done to make a system safe against these flaws that might become hard to trace?
