| Summary: | subversion fails with USE='-berkdb' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Maarten Billemont <lhunath> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2005.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Maarten Billemont
2006-01-10 12:19:02 UTC
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? 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? |
