Summary: | sys-apps/portage-2.1.11.50: emerge -a offers to add package to world when it's already in world | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robin Bankhead <gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | minor | Keywords: | InVCS |
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 456888 |
Description
Robin Bankhead
2013-02-07 01:10:34 UTC
The is how it's intended to behave unless you add --oneshot to your options. Alternatively, you can set --select=n in EMERGE_DEFAULT_OPTS, and use the --select option when you want to add something to the world file. It's surely not intended for it to offer to add a package to world that's *already in* world? (Sorry if that was underemphasised above, I did mention it.) When the prompt occurs, it hasn't checked whether or not the package(s) are in the world file yet. So, we'll have to refactor the code a bit if we want it to have that information there. It would make sense from a transparency point of view: since the prompt (and the message) is spurious in this scenario, it would be best eliminated. The cost of checking world state at that point can't be all that onerous I'd have thought. It also occurs that folks might assume that answering "no" would actually *remove* the atom from the world file, which it doesn't. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=87d1b397eb61b51c657806a29a09828b6ad55137 This is fixed in 2.1.11.51 and 2.2.0_alpha162. |