summaryrefslogtreecommitdiffstats
path: root/doc/config/sets.docbook
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2011-05-21 17:46:11 -0700
committerZac Medico <zmedico@gentoo.org>2011-05-25 20:51:11 -0700
commit0a7d76f7ea98aaa041a314f607e46cc7f81ce588 (patch)
tree05c9a407b342f1e09871127afdc536721af4a0cd /doc/config/sets.docbook
parenteaace2f20c6a9b1f1244997dcf5f4ac85623a4a4 (diff)
downloadportage-0a7d76f7ea98aaa041a314f607e46cc7f81ce588.tar.gz
portage-0a7d76f7ea98aaa041a314f607e46cc7f81ce588.tar.bz2
portage-0a7d76f7ea98aaa041a314f607e46cc7f81ce588.zip
DepPriority: remove "rebuild" attribute
Since the addition of DepPriorityNormalRange and DepPrioritySatisfiedRange in commit bd369956b2a2fbc019a655a372628998499156c0, which solves most cases of bug 199856, the Depriority.rebuild attribute doesn't appear to make any difference. The edges that this attribute differentiates are already naturally differentiated by the fact that the child node of a satisfied buildtime dependency that's not being rebuilt will naturally be identified as a leaf node earlier and removed from the graph, thereby eliminating the edge before there's an opportunity to compare it with a higher priority rebuild edge. The addition of the "optional" attribute (in commit 15476805a156acd11fdaaa19212691e8ee09b309) also plays a role here, since it converts some satisfied buildtime edges to optional edges, thereby reducing their priority.
Diffstat (limited to 'doc/config/sets.docbook')
0 files changed, 0 insertions, 0 deletions