Summary: | sys-apps/portage: poor "die on mask changes" handling | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeremy Olexa (darkside) (RETIRED)
2011-06-03 15:58:13 UTC
At a minimum, I guess we need to make the autounmask code suggest to use --autounmask=n so that it's easy for users to recognize that this is an option. You may want set --autounmask=n in EMERGE_DEFAULT_OPTS until you get your masks working like you want them to, or until you can get a more recent version of dbus to build. I've added a note: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d21811eec723ffc6acb1daf0e2d7b19bf3af6978 It looks like this: NOTE: This --autounmask behavior can be disabled by setting EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf. I suspect that this will be sufficient for general use, since the case of dealing with unsatisfied dependencies triggered by local masks only represents a minority of dependency calculations, and you can always set EMERGE_DEFAULT_OPTS="--autounmask=n" temporarily if you happen to find yourself in this mode. That said, it might also be nice to have the ability to do something like --autounmask-local-mask=n to disable autounmask just for local masks. *** This bug has been marked as a duplicate of bug 372485 *** |