Summary: | etc-update: Support mv_opts for -5 auto-merge | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Doug Weimer <dougw> |
Component: | Tools | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | tools-portage |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949, 187293 | ||
Attachments: | Removes -i rather than all mv_opts |
Description
Doug Weimer
2004-04-10 10:51:21 UTC
Created attachment 29036 [details, diff]
Removes -i rather than all mv_opts
This patch is against /usr/sbin/etc-update from portage-2.0.50-r3. It makes the
following change:
- export mv_opts=""
+ export mv_opts=${mv_opts//-i/};
better patch: export mv_opts=" ${mv_opts} " mv_opts="${mv_opts// -i }" It's probably due to a misunderstanding of the changes, but I can't see the improvement. The new version seems to produce the following for various mv_opts settings: 1. "-i" -> "" 2. "-b -i" or "-i -b" -> extra leading or trailing whitespace 3. "--backup=existing -i --suffix=^" -> mv failure correct patch: export mv_opts=" ${mv_opts} " mv_opts="${mv_opts// -i / }" Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;) Reopening for consideration This has been released in 2.1.2.10. |