# debtree — package dependency graphs on steroids

### Introduction ### Example: debconf Graph from apt-cache (for comparison) Basic graph (only hard dependencies and conflicts) Basic graph with Recommends Basic graph with Recommends and Suggests Basic graph with Recommends and showing alternatives Default graph (showing Recommends, alternatives and versions) Default graph with Suggests Default graph with Suggests and versioned Conflicts Default graph (rotated) Shown are: Pre-Depends, Depends, unversioned Conflicts and relevant Provides. This is one of the most basic graphs that can be generated. Only the Conflicts and the virtual package `debconf-2.0` that `debconf` provides could have been suppressed. The graph also shows the full set of packages that provide `debconf-2.0`. The square brackets around `debconf` indicate that the package is also displayed elsewhere in the graph, while the braces around `cdebconf` indicate that the dependency info for that package is not included in the graph. `perlapi-5.10.0` is a virtual package provided by `perl-base`. A virtual package is only displayed if it is provided by the requested package, or if it is a dependency or conflict from some package included in the graph. Some packages, like `libc6` and `zlib1g`, have been excluded from all graphs as so many packages depend on them that they only cause clutter without adding any real information; it would be nice to show them in some other way. The reddish shade of `debconf-tiny` means that the package is unknown (does not exist in the package database). Note the circular dependency between `debconf` and `debconf-i18n`. |  | `$ debtree --no-recommends --no-alternatives --no-versions debconf`
Generated .dot file: | DOT
Full-sized images: | PS | PNG | SVG
Equivalent graph for aptitude