Summary: | emerge -e world improvemenmt | ||
---|---|---|---|
Product: | Portage Development | Reporter: | David Carlos Manuelda <StormByte> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Carlos Manuelda
2011-03-14 03:32:00 UTC
I forgot to add, that they will be built anyway, so a change in its order will not harm anyone, but will benefit. I gets messy hardcoding logic like this into the merge order calculations. We already have some special code for glibc version changes, since it's needed to avoid broken systems (bug #303567). Note that you can get similar results like this: emerge gcc glibc && emerge -e world --exclude gcc --exclude glibc how is this any different from Bug 283422 which you already filed ? *** This bug has been marked as a duplicate of bug 283422 *** |