Summary: | [PATCH] sys-apps/portage - emerge: avoid updates unless --update option is enabled | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sebastian Luther (few) <SebastianLuther> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | betelgeuse, gentoo-bugs |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=525052 https://bugs.gentoo.org/show_bug.cgi?id=559354 https://bugs.gentoo.org/show_bug.cgi?id=646466 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 280394, 288499 | ||
Attachments: |
emerge: introdue --avoid-update option
emerge: introduce --avoid-update option |
Description
Sebastian Luther (few)
2009-06-30 12:32:11 UTC
Created attachment 196152 [details, diff]
emerge: introdue --avoid-update option
Would it not be better (and more intuitive) to only consider newer versions of packages if --update is specified? Also, the patch appears to add --avoid-packages to the man page, but this option isn't included anywhere else in the patch. (In reply to comment #2) > Would it not be better (and more intuitive) to only consider newer versions of > packages if --update is specified? Like the man page entry says, it may lead to slot conflicts and without bug 1343 solved, this is not going to change. > Also, the patch appears to add --avoid-packages to the man page, but this > option isn't included anywhere else in the patch. Have a look at the attached file. Everyone interested in this should have a look at bug 275898. Created attachment 196158 [details, diff]
emerge: introduce --avoid-update option
Corrected --avoid-package -> --avoid-update in the man page, thanks to AllenJB.
Thanks, this is in svn r13745. (In reply to comment #2) > Would it not be better (and more intuitive) to only consider newer versions of > packages if --update is specified? Good idea, that's how it is now in svn r13772. This is fixed in 2.2_rc34. *** Bug 158358 has been marked as a duplicate of this bug. *** This is fixed in 2.1.7. |