Summary: | --usepkgonly ignores --noreplace | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Åsmund Grammeltvedt <asmundg.bugs.gentoo.org> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Åsmund Grammeltvedt
2006-09-11 02:38:38 UTC
It is correct. --noreplace means not to reinstall if the version chosen is the same version as that already installed (if installed). If there are no packages available, it's impossible to reach that check. # emerge -p --noreplace foobar These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] app-portage/foobar-1.1 [1.0] (Didn't close in case somebody thinks it worth changing the behaviour of --noreplace) Hm, seems like my last reponse got lost somewhere. My main issue with this behaviour is that it makes it difficult to provide a set of binary packages and have a host use these to upgrade _if_ a newer version of an installed package is available. This is of course possible to achieve with some scripting, but the semantics of --usepkgonly and --noreplace appeared, based on the emerge(1) documentation, to provide what I wanted. Anyway, thanks for the clarifying comments. As Jason said. The only viable alternative IMHO would be to treat vdb as another binrepo to use for --usepkgonly, but that would be another bug. |