Bug 384003 – sys-apps/portage: Implement --complete-graph-if-new-ver

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Sebastian Luther (few) 2011-09-21 18:29:40 UTC]

<few_> what I actually want is a cache for dependency atoms that aren't unrestricted or are of >= type
<few_> to prevent emerge from installing foo-2 if some installed package depends on <foo-2
<zmedico> few_: it's probably not worth the trouble when you could just enable --complete-graph
<few_> zmedico: oh, you want to enable --complete-grapg by default now?
<zmedico> few_: no, but it's there for those who need it. it depends on use cases. generally, it just wastes time
<zmedico> few_: we already trigger --complete-graph for downgrades. maybe we should do it for upgrades too, and possibly add an option to disable this for those who feel they don't need it
<zmedico> few_: I think I'll call it --complete-graph-if-version-changed, and enable by default
<zmedico> few_: I'm going to disable this one locally, because the downgrade trigger is already wasting my time
<few_> zmedico: sounds good.
<few_> I put --complete-graph in EMERGE_DEFAULT_OPTS on every system I get my hands on btw.

[Comment 1 Zac Medico 2011-09-21 19:43:07 UTC]

This is in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2733ea17d8e25db8dd369e8890337ddb553e2509

[Comment 2 Zac Medico 2011-09-29 18:48:24 UTC]

This is fixed in 2.1.10.20 and 2.2.0_alpha60.