blob: 79060734174389a1ce2445579f5a5b9a46f5d5b7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
.\" This manpage has been automatically generated by docbook2man
.\" from a DocBook document. This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "RPMGRAPH" "8" "30 June 2002" "Red Hat, Inc." "Red Hat Linux"
.SH NAME
rpmgraph \- Display RPM Package Dependency Graph
.SH SYNOPSIS
.PP
\fBrpmgraph\fR \fB\fIPACKAGE_FILE\fB\fR\fI ...\fR
.SH "DESCRIPTION"
.PP
\fBrpmgraph\fR uses \fIPACKAGE_FILE\fR arguments
to generate a package dependency graph. Each
\fIPACKAGE_FILE\fR argument is read and
added to an rpm transaction set. The elements of the transaction
set are partially ordered using a topological sort. The partially
ordered elements are then printed to standard output.
.PP
Nodes in the dependency graph are package names, and edges in the
directed graph point to the parent of each node. The parent node
is defined as the last predecessor of a package when partially ordered
using the package dependencies as a relation. That means that the
parent of a given package is the package's last prerequisite.
.PP
The output is in \fBdot\fR(1) directed graph format,
and can be displayed or printed using the \fBdotty\fR
graph editor from the \fBgraphviz\fR package.
There are no \fBrpmgraph\fR specific options, only common \fBrpm\fR options.
See the \fBrpmgraph\fR usage message for what is currently implemented.
.SH "SEE ALSO"
\fBdot\fR(1),
\fBdotty\fR(1),
\fB http://www.graphviz.org/ <URL:http://www.graphviz.org/>
\fR
.SH "AUTHORS"
Jeff Johnson <jbj@redhat.com>
|
