pkgcore.ebuild.resolver module

resolver configuration to match portage behaviour (misbehaviour in a few spots)

pkgcore.ebuild.resolver.min_install_resolver(vdbs, dbs, verify_vdb=True, nodeps=False, force_replace=False, resolver_cls=<class 'pkgcore.resolver.plan.merge_plan'>, **kwds)

Resolver that tries to minimize the number of changes while installing.

generate and configure a resolver that is focused on just installing requests- installs highest version it can build a solution for, but tries to avoid building anything not needed

Parameters:

• vdbs – list of pkgcore.repository.prototype.tree instances that represents the livefs

• dbs – list of pkgcore.repository.prototype.tree instances representing sources of pkgs

• verify_vdb – should we stop resolving once we hit the vdb, or do full resolution?

Returns:

pkgcore.resolver.plan.merge_plan instance

pkgcore.ebuild.resolver.upgrade_resolver(vdbs, dbs, verify_vdb=True, nodeps=False, force_replace=False, resolver_cls=<class 'pkgcore.resolver.plan.merge_plan'>, **kwds)

generate and configure a resolver for upgrading all processed nodes.

Parameters:

• vdbs – list of pkgcore.repository.prototype.tree instances that represents the livefs

• dbs – list of pkgcore.repository.prototype.tree instances representing sources of pkgs

• verify_vdb – should we stop resolving once we hit the vdb, or do full resolution?

Returns:

pkgcore.resolver.plan.merge_plan instance