aptpkg::source(3pm) [debian man page]
AptPkg::Source(3pm) User Contributed Perl Documentation AptPkg::Source(3pm) NAME
AptPkg::Source - APT source package interface SYNOPSIS
use AptPkg::Source; DESCRIPTION
The AptPkg::Source module provides an interface to APT's source package lists. AptPkg::Source The AptPkg::Source package implements the APT pkgSrcRecords class as a hash reference (inherits from AptPkg::hash). The hash is keyed on source or binary package name and the value is an array reference of the details of matching source packages. Note that there is no iterator class, so it is not possible to get a list of all keys (with keys or each). Constructor new([SOURCELIST]) Instantiation of the object uses configuration from the $AptPkg::Config::_config object (automatically initialised if not done explicitly). If no SOURCELIST is specified, then the value of Dir::Etc::sourcelist from the configuration object is used (generally /etc/apt/sources.list). Methods find(PACK, [SRCONLY]) In a list context, return a list of source package details for the given PACK, which may either be a source package name, or the name of one of the binaries provided (unless SRCONLY is provided and true). In a scalar context, the source package name of the first entry is returned. get, exists These methods are used to implement the hashref abstraction: $obj->get($pack) and $obj->{$pack} are equivalent. The get method has the same semantics as find, but returns an array reference in a scalar context. The list returned by the find (and get) methods consists of hashes which describe each available source package (in order of discovery from the deb-src files described in sources.list). Each hash contains the following entries: Package Version Maintainer Section Strings giving the source package name, version, maintainer and section. Binaries A list of binary package names from the package. BuildDepends A hash describing the build dependencies of the package. Possible keys are: "Build-Depends", "Build-Depends-Indep", "Build-Conflicts", "Build-Conflicts-Indep". The values are a list of dependencies/conflicts with each item being a list containing the package name followed optionally by an operator and version number. Operator values evaluate to a comparison string* (>, >=, etc) or one of the AptPkg::Dep:: constants in a numeric context (see "pkgCache::Dep::DepCompareOp" in AptPkg(3pm)). *Note that this is a normalised, rather than Debian-style (>> vs >) string. Files A list of files making up the source package, each described by a hash containing the keys: "MD5Hash", "Size", "ArchiveURI", "Type". SEE ALSO
AptPkg::Config(3pm), AptPkg::Cache(3pm), AptPkg(3pm), AptPkg::hash(3pm). AUTHOR
Brendan O'Dea <bod@debian.org> perl v5.14.2 2012-03-16 AptPkg::Source(3pm)
Check Out this Related Man Page
APT-RDEPENDS(1) APT-RDEPENDS(1) NAME
apt-rdepends - performs recursive dependency listings similar to apt-cache SYNOPSIS
apt-rdepends [options] [pkgs ...] DESCRIPTION
apt-rdepends searches through the APT cache to find package dependencies. apt-rdepends knows how to emulate the result of calling apt- cache with both depends and dotty options. By default, apt-rdepends shows a listing of each dependency a package has. It will also look at each of these fulfilling packages, and recursively lists their dependencies. OPTIONS
-b, --build-depends Show build dependencies instead of normal package dependencies. -d, --dotty dotty takes a list of packages on the command line and generates output suitable for use by springgraph (1). The result will be a set of nodes and edges representing the relationships between the packages. By default the given packages will trace out all dependent packages which can produce a very large graph. Blue lines are pre-depends, green lines are conflicts, yellow lines are suggests, orange lines are recommends, red lines are replaces, and black lines are depends. Caution, dotty cannot graph larger sets of packages. -p, --print-state Shows the state of each dependency after each package version. See --state-follow and --state-show for why this is useful. -r, --reverse Shows the listings of each package that depends on a package. Furthermore, it will look at these dependent packages, and find their dependers. -f, --follow=DEPENDS A comma-separated list of DEPENDS types to follow recursively. By default, it only follows the Depends and PreDepends types. The possible values for DEPENDS are: Depends, PreDepends, Suggests, Recommends, Conflicts, Replaces, and Obsoletes. In --build-depends mode, the possible values are: Build-Depends, Build-Depends-Indep, Build-Conflicts, Build-Conflicts-Indep. -s, --show=DEPENDS A comma-separated list of DEPENDS types to show, when displaying a listing. By default, it only shows the Depends and PreDepends types. --state-follow=STATES --state-show=STATES These two options are similar to --follow and --show. They both deal with the current state of a package. By default, the value of STATES is Unknown, NotInstalled, UnPacked, HalfConfigured, HalfInstalled, ConfigFiles, and Installed. These options are useful, if you only want to only look at the dependencies between the Installed packages on your system. You can then call: apt-rdepends --state-follow=Installed libfoo Or if you want to only show the packages installed on your system: apt-rdepends --state-follow=Installed --state-show=Installed libfoo pkgs The list of packages on which to discover dependencies. -v, --vcg, --xvcg This option takes a list of packages on the command line and generates output suitable for use by xvcg. The result will be a set of nodes and edges representing the relationships between the packages. By default the given packages will trace out all dependent packages which can produce a very large graph. Blue lines are pre-depends, green lines are conflicts, yellow lines are suggests, orange lines are recommends, red lines are replaces, and black lines are depends. -o, --option=OPTION Set an APT Configuration Option; This will set an arbitrary configuration option. The syntax is -o Foo::Bar=bar. SEE ALSO
apt.conf(5), sources.list(5), apt-cache(8), AptPkg(3), springgraph(1) BUGS
apt-rdepends does not emulate apt-cache perfectly. It does not display information about virtual packages, nor does it know about virtual packages when it is in reverse dependency mode. apt-rdepends also does not know how to stop after a certain depth has been reached. apt-rdepends cannot do reverse build-dependencies. This is really difficult, since it would have to load the whole cache into memory before discovering which packages depend on others to build. apt-rdepends exists. This functionality should really reside in apt-cache itself. AUTHOR
apt-rdepends was written by Simon Law <sfllaw@debian.org> 1.3.0 2012-09-16 APT-RDEPENDS(1)