Summary: | An Overlay Switch? | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Chandler Paul <coollyude> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | coollyude |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 240187 |
Description
Chandler Paul
2011-09-10 22:32:28 UTC
Since portage-2.1.10 you can add repo atoms to the world file in order to set these kinds of preferences. For example: emerge --noreplace sys-apps/dbus::gentoo That will for updates to pull dbus from the gentoo repo. You can also use repo atoms to mask package. For example, put "sys-apps/dbus::gnome" in /etc/portage/package.mask, in order to mask dbus from the gnome overlay. (In reply to comment #1) > Since portage-2.1.10 you can add repo atoms to the world file in order to set > these kinds of preferences. As it is, this feature is pretty usable. However, we could improve my making the dependency graph account for these kinds of world atoms in more cases (when @world is not explicitly pulled into the graph). (In reply to comment #2) > (In reply to comment #1) > > Since portage-2.1.10 you can add repo atoms to the world file in order to set > > these kinds of preferences. > > As it is, this feature is pretty usable. However, we could improve my making > the dependency graph account for these kinds of world atoms in more cases (when > @world is not explicitly pulled into the graph). I'd say these small tweaks should get their own bugs, otherwise they get lost in the too general "repo support" bugs. |