pmerge¶

Synopsis¶

pmerge [-h] [–version] [–debug] [-q] [-v] [–color BOOLEAN] [–config CONFIG_PATH] [–domain DOMAIN] [-u | -d | -C | –clean | –list-sets] [-p] [-a] [-f] [-1] [-D] [-N] [-i] [–with-bdeps] [-O] [-o] [-n] [-b] [-k] [-K] [-S] [-e] [-x TARGET[,TARGET,…]] [–ignore-failures] [–force] [–preload-vdb-state] [–quiet-repo-display] [-F FORMATTER] [–pdb-intercept TARGET[,TARGET,…]] [–disable-resolver-target-sorting] [TARGET …]

Portage Compatibility¶

With regards to portage compatibility, pmerge provides much of the same functionality that emerge(1) does. In general, it should be possible to use both pmerge and emerge on the same system in a sane fashion. For example, pmerge can be used to install packages and then emerge should be able to upgrade or uninstall them, or vice versa. Also, binary packages created using pmerge should be able to be installed properly using emerge. Any major compatibility issue that arises when trying to use both package managers is probably a bug and should be reported.

In terms of option naming, pmerge tries to remain somewhat compatible to portage so running pmerge -1av should work the same as emerge -1av when using portage. However, pmerge doesn’t implement nearly the same amount of options that portage provides so many of the more obscure ones are missing. In addition, pmerge defaults to a portage compatible output format that closely matches the default colors and output structure that portage uses.

Positional Arguments¶

TARGET: extended package matching

Base Options¶

-h, --help: show this help message and exit
--version: show this program’s version info and exit
--debug: enable debugging checks
-q, --quiet: suppress non-error messages
-v, --verbose: show verbose output
--color BOOLEAN: enable/disable color support

Config Options¶

--config CONFIG_PATH: use custom config or skip loading system config
--domain DOMAIN: custom pkgcore domain to use for this operation

Operations¶

-u, --upgrade: try to upgrade installed pkgs/deps
-d, --downgrade: try to downgrade installed pkgs/deps
-C, --unmerge: unmerge packages
--clean: remove installed packages not referenced by any target pkgs/sets
--list-sets: display the list of available package sets

Resolver Options¶

-p, --pretend: only perform the dep resolution
-a, --ask: ask for user confirmation after dep resolution
-f, --fetchonly: do only the fetch steps of the resolved plan
-1, --oneshot: do not record changes in the world file
-D, --deep: force the resolver to verify installed deps
-N, --newuse: add installed pkgs with changed useflags to targets
-i, --ignore-cycles: ignore unbreakable dep cycles
--with-bdeps: process build deps for built packages
-O, --nodeps: disable dependency resolution
-o, --onlydeps: only merge the deps of the specified packages
-n, --noreplace: don’t reinstall target pkgs that are already installed
-b, --buildpkg: build binpkgs
-k, --usepkg: prefer to use binpkgs
-K, --usepkgonly: use only binpkgs
-S, --source-only: use only ebuilds, no binpkgs
-e, --empty: force rebuilding of all involved packages
-x TARGET[,TARGET,...], --exclude TARGET[,TARGET,...]: inject packages into the installed set
--ignore-failures: ignore failures while running all types of tasks
--force: force changes to a repo, regardless of if it’s frozen
--preload-vdb-state: enable preloading of the installed packages database

Output Options¶

--quiet-repo-display: use indexes instead of ::repo suffixes in dep resolution output
-F FORMATTER, --formatter FORMATTER: output formatter to use

Resolver Debugging Options¶

--pdb-intercept TARGET[,TARGET,...]: trigger a pdb.set_trace() for any resolver decisions that match this restriction
--disable-resolver-target-sorting: disable stabilization of resolver graph processing

Example Usage¶

Merge pkgcore from the gentoo repo:

pmerge sys-apps/pkgcore::gentoo

Output a simple list of package atoms that would be updated for a global update:

pmerge -uDp --formatter basic @world

Force new binpkgs to be built for the entire system set using a custom configuration directory:

pmerge -uDSeb --config /home/foo/portage @system