Summary: | add new emerge --select[=n] option for making --oneshot behavior default | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nils Stöckmann <accounts> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | ulenrich |
Priority: | High | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 288499 |
Description
Nils Stöckmann
2009-10-06 09:17:05 UTC
You can set EMERGE_DEFAULT_OPTS="--oneshot" in make.conf. How about if we also add a --select=<y|n> option, to complement --deselect? We could make --select=n equivalent to --oneshot, and --select=y would be the opposite. it took me a few minutes to think about, but that sounds perfect. --select=y would then be the method adding the atom to the worldfile and part of the default emerge process. specifing "--select" on command line would override a specified --oneshot (i.e. within EMERGE_DEFAULT_OPTS) then and record the emerged atom after a successful merge. If I understood you right and that's what you meant, I'd be perfectly fine with the idea. This is fixed in svn r14615. This is fixed in 2.1.7.2 and 2.2_rc47. *** Bug 707924 has been marked as a duplicate of this bug. *** |