Summary: | Failing to bring in dependancies at depth > 1. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robin Johnson <robbat2> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | alex_y_xu, kfm |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robin Johnson
![]() ![]() ![]() ![]() It's assumed that since libgksu is installed, it's dependencies must already be satisfied. It's always been this way without --deep, and enabling --deep by default would carry a performance penalty for every little dependency calculation. Just one additional question then: Which copy of the RDEPEND is being used? The ones stored in vardb or the ones from the latest ebuild? RDEPEND comes from the latest ebuild, but that might change for EAPI 3, as mentioned in bug 282927, comment #3. *** Bug 298909 has been marked as a duplicate of this bug. *** |