| 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
| 2 |
<html lang="en"> |
| 3 |
<head> |
| 4 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
| 5 |
<title>debtree - Package dependency graphs</title> |
| 6 |
</head> |
| 7 |
|
| 8 |
<body> |
| 9 |
<h1>debtree — package dependency graphs on steroids</h1> |
| 10 |
|
| 11 |
<table> |
| 12 |
<tbody valign="top"> |
| 13 |
<tr> |
| 14 |
<td> |
| 15 |
<h3><a href="index.html">Introduction</a></h3> |
| 16 |
|
| 17 |
<h3>Advanced usage examples</h3> |
| 18 |
|
| 19 |
<ol> |
| 20 |
<li><b>Create a build dependency graph</b></li> |
| 21 |
<li><a href="usage2.html">Visualize what would happen when installing a package</a></li> |
| 22 |
<li><a href="usage3.html">Dependencies on virtual packages</a></li> |
| 23 |
<li><a href="usage4.html">Reverse dependencies</a></li> |
| 24 |
</ol> |
| 25 |
<hr /> |
| 26 |
|
| 27 |
<p> |
| 28 |
This example shows a basic build dependency graph for <tt>dpkg</tt>. |
| 29 |
Alternatives and Suggests are suppressed by default and Recommends and Conflicts |
| 30 |
have been suppressed using command line options. This graph represents what gets |
| 31 |
installed on a buildd when <tt>dpkg</tt> is built. |
| 32 |
</p><p> |
| 33 |
The <tt>--show-all</tt> option could have been used to also show dependencies on |
| 34 |
packages like <tt>libc6</tt>. In this case the resulting graph is still manageable. |
| 35 |
</p><p> |
| 36 |
In this case only Build-Depends are shown. If present, Build-Depends-Indep are |
| 37 |
indicated by lines that are thinner and a bit lighter in color. |
| 38 |
</p><p> |
| 39 |
By default the graph is generated for the architecture on which it is generated. |
| 40 |
In that case the "arch conditions" for the build dependency on <tt>libselinux1-dev</tt> |
| 41 |
would not have been displayed. They are in this graph because of the <tt>arch=all</tt> |
| 42 |
option. If the graph had been generated on a system running hurd-i386, the |
| 43 |
dependency on <tt>libselinux1-dev</tt> would not have been shown at all. |
| 44 |
</p><p> |
| 45 |
Note that if you generate a graph for an architecture other than your system's, |
| 46 |
the dependency information for some packages may not be available. These packages |
| 47 |
will get a reddish shade. |
| 48 |
</p><p> |
| 49 |
If you'd like to see what you need to install on your own system to build a |
| 50 |
package, use the <tt>-I</tt> option. In that case alternatives will not be |
| 51 |
automatically suppressed. |
| 52 |
</p><p> |
| 53 |
For a nice, though somewhat extreme, example of a graph showing architecture |
| 54 |
conditions, give this a try: |
| 55 |
</p><p> |
| 56 |
<tt><font size="-1"> |
| 57 |
$ debtree -b --arch=all --no-recommends --no-conflicts debian-installer |
| 58 |
</font></tt> |
| 59 |
</p> |
| 60 |
|
| 61 |
</td> |
| 62 |
<td width="10" /> |
| 63 |
<td width="400"> |
| 64 |
|
| 65 |
<p><tt><font size="-1"> |
| 66 |
$ debtree -b --arch=all --no-recommends --no-conflicts dpkg |
| 67 |
</font></tt></p> |
| 68 |
<hr /> |
| 69 |
<img src="thumbs/usage1.png" alt="Build dependency graph for dpkg" /> |
| 70 |
<hr /> |
| 71 |
<table> |
| 72 |
<tr> |
| 73 |
<td>Generated .dot file:</td> |
| 74 |
<td><a href="usage1.dot">DOT</a></td> |
| 75 |
</tr><tr> |
| 76 |
<td>Full-sized images:</td> |
| 77 |
<td><a href="usage1.ps" target="_blank">PS</a> | PNG | <a href="usage1.svg" target="_blank">SVG</a></td> |
| 78 |
</tr> |
| 79 |
</table> |
| 80 |
|
| 81 |
</td> |
| 82 |
</tr> |
| 83 |
</tbody> |
| 84 |
</table> |
| 85 |
|
| 86 |
</body> |
| 87 |
</html> |