Summary: | emerge --update does too much! | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Henk de Leeuw <gentoo-bugzilla> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | greg_g |
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Henk de Leeuw
2003-06-08 03:46:36 UTC
I don't have a personal opinion on this, but maybe the devs have decided so because otherwise `emerge --upgrade' would be the same as plain `emerge' (more precisely, would be the same as `emerge --noreplace'. That is something I had not considered yet. But I still fail to see the use of automatically updating first-level (and first-level only!) dependencies. Especially because -U implies -u. I have several packages that I have chosen manually from ~x86. So, when updating, I have to use -U, to prevent automatic downgrading. But -U implies -u, so when I upgrade a small package that depends on a large package, I run the risk of updating that large package as well, even if the older version of the large package would be perfectly acceptable to the new small package (and to me!). I know that there are tricks you can use to prevent this (editing your world file manually, portage overlay dir, etc), but I think that a lot of these tricks would not be necessary if --upgrade did the same as --noreplace does now (or -U implied -n instead of -u). What am I missing here? The current behaviour of --update must have reasons that I have failed to see yet. Use 49-r18 or the latest 2.0.50 series. /etc/portage/package.keywords |