Summary: | portage doesn't handle !some/ebuild dependencies correct | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Carsten Lohrke (RETIRED)
![]() btw. gnome-themes is missing "!>=x11-themes/gtk-engines-mist-0.10" $ emerge -p gtk-engines-mist These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10 oh, and the other one would be a bug for the gnome team, please file a new bug for that. to verify this, you have to unmerge x11-themes/gnome-themes and all ebuilds that depend on it, merge gtk-engines-mist-0.10 and wonder, why portage wants to force you to install x11-themes/gnome-themes and the other two gtk ebuilds, it depends on. that merging gtk-engines-mist is blocked by gnome-themes is obvious, but not my point. $ emerge -ep gtk-engines-mist | grep theme [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10 $ USE="-*" emerge -ep gtk-engines-mist | grep theme [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10 will try with unmerging and merging later, but I don't think that the result will be different. |