| Trees | Indices | Help |
|
|---|
|
|
object --+
|
portage.dbapi.dbapi --+
|
_dep_check_composite_db
A dbapi-like interface that is optimized for use in dep_check() calls. This is built on top of the existing depgraph package selection logic. Some packages that have been added to the graph may be masked from this view in order to influence the atom preference selection that occurs via dep_check().
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from Inherited from |
|||
|
|||
|
Inherited from |
|||
|
|||
|
Inherited from |
|||
|
|||
|
Inherited from Inherited from |
|||
|
|||
x.__init__(...) initializes x; see help(type(x)) for signature
|
Emulate cp_list just so it can be used to check for existence of new-style virtuals. Since it's a waste of time to return more than one cpv for this use case, a maximum of one cpv will be returned.
|
Given a dependency, try to find packages that match
Args:
origdep - Depend atom
use_cache - Boolean indicating if we should use the cache or not
NOTE: Do we ever not want the cache?
Returns:
a list of packages that match origdep
|
Return the metadata keys in mylist for mycpv
Args:
mycpv - "sys-apps/foo-1.0"
mylist - ["SLOT","DEPEND","HOMEPAGE"]
myrepo - The repository name.
Returns:
a list of results, in order of keys in mylist, such as:
["0",">=sys-libs/bar-1.0","http://www.foo.com"] or [] if mycpv not found'
|
| Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Tue Jun 18 14:31:41 2013 | http://epydoc.sourceforge.net |