Summary: | sys-apps/portage: emerge -1kB unpacks binpackages to tempdir and exits | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michał Górny
2019-09-23 16:02:41 UTC
I wonder if passing --buildpkgonly should disable --usepkg and --usepkgonly, or if emerge should just immediately exit with an error message given this combination of flags. It doesn't clean ${PORTAGE_TMPDIR} because that normally happens after merge and the packages are never merged in --buildpkgonly mode. (In reply to Mike Gilbert from comment #1) > I wonder if passing --buildpkgonly should disable --usepkg and --usepkgonly, > or if emerge should just immediately exit with an error message given this > combination of flags. --usepkgonly should definitely be an error, but --usepkg or --getbinpkg in EMERGE_DEFAULT_OPTS could be tolerated as long as we make them moot like this: > diff --git a/lib/_emerge/depgraph.py b/lib/_emerge/depgraph.py > index 51614fc14..17559ca84 100644 > --- a/lib/_emerge/depgraph.py > +++ b/lib/_emerge/depgraph.py > @@ -573,7 +573,8 @@ class _dynamic_depgraph_config(object): > db_keys = list(portdb._aux_cache_keys) > dbs.append((portdb, "ebuild", False, False, db_keys)) > > - if "--usepkg" in depgraph._frozen_config.myopts: > + if ("--usepkg" in depgraph._frozen_config.myopts and > + "--buildpkgonly" not in depgraph._frozen_config.myopts): > bindb = depgraph._frozen_config.trees[myroot]["bintree"].dbapi > db_keys = list(bindb._aux_cache_keys) > dbs.append((bindb, "binary", True, False, db_keys)) |