Summary: | sys-apps/portage-2.2.8-r2 : --newuse should win over --with-bdeps=n | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Fab <netbox253> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723 | ||
Attachments: | emerge --info |
Description
Fab
2014-11-03 14:57:49 UTC
(In reply to Fab from comment #0) > The last three packages will be rebuilt with USE="-minimal". > I think --newuse should win over --with-bdeps=n. Those packages will not even be pulled into the dependency graph unless you use --with-bdeps=y, and it's not possible to apply --newuse to packages that have not been pulled into the dependency graph. In fact, packages that are not pulled into the dependency graph are eligible for removal, in order to solve blockers. Furthermore, it's possible to use 'emerge --depclean --with-bdeps=n` to remove those packages. It's not possible for emerge to guess your intentions, therefore you have to explicitly specify --with-bdeps=y if that's the behavior that you want. Note that it's possible that we could add a --with-bdeps=auto which would trigger something similar to the behavior that you have asked for. However, it's not possible to do it within the context of the current --with-bdeps=[y|n] model. Ok. I wanted to be sure this was not a bug before doing anything. I was not aware of this behavior. Then I will add --with-bdeps=y to EMERGE_DEFAULT_OPTS. Thanks for the explanation. |