Summary: | portage 2.1.2-r9, emerge order weird for --empty | ||
---|---|---|---|
Product: | Portage Development | Reporter: | devsk <funtoos> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS, REGRESSION |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 167107 | ||
Attachments: | optimize merge order by delaying the merge of root nodes |
Description
devsk
2007-02-18 10:41:05 UTC
This behavior is triggered by a circular dependency between gpm and ncurses. I'll see about improving the merge order calculation logic for cases like this. Created attachment 110583 [details, diff] optimize merge order by delaying the merge of root nodes With this patch, I get the following order: [ebuild R ] sys-libs/ncurses-5.6 [ebuild R ] app-shells/bash-3.2_p9-r1 [ebuild R ] sys-libs/gpm-1.20.1-r5 Though this order is different from that produced by 2.1.1, it's just as good. The difference is due to the building of a complete dependency graph (bug #147766). In svn r6010 I've optimized leaf node selection by ordering nodes from highest to lowest overall reference count. This leads to the following merge order: [ebuild R ] sys-libs/ncurses-5.6 [ebuild R ] sys-libs/gpm-1.20.1-r5 [ebuild R ] app-shells/bash-3.2_p9-r1 This has been released in 2.1.2-r10. |