Summary: | emerge does not consider a stable package version if an overlay has the same version, but not marked stable | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nico R. <n-roeser> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nico R.
2008-07-02 09:09:29 UTC
This *is* why it's called an overlay. It.. lays itself over the official tree. Ummm… IIRC, if there is a newer version in the official tree and not in the overlay, the newer version is used. IMHO, this should also happen in the case I described in comment 0. So if it lays itself over the official tree, that tree should “shine through” for ebuilds where the overlay cannot be used (due to masks etc.); I’d say the overlay should become “transparent” in these areas. *** This bug has been marked as a duplicate of bug 185377 *** |