Summary: | portage in cross environment always tries to fetch dependencies of host environment | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alon Bar-Lev (RETIRED) <alonbl> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | xemerge |
Description
Alon Bar-Lev (RETIRED)
2007-11-23 09:19:07 UTC
Created attachment 136743 [details]
xemerge
This is the xemerge script I use.
The problem is that DEPEND, RDEPEND, and PDEPEND are insufficient to fully model the types of dependency relationships that exist in a cross environment (bug 174552). With the current types, the designed behavior is to merge only DEPEND to the host system and all 3 types to the cross-compiled system. (In reply to comment #2) > With the current types, the designed behavior is to merge only DEPEND to the > host system and all 3 types to the cross-compiled system. Err, that's wrong. It's DEPEND to the host system, and only RDEPEND and PDEPEND to the cross-compiled system. Thanks! I thought that specifying ROOT should force portage to look at the ROOT for all dependencies. *** This bug has been marked as a duplicate of bug 174552 *** |