blob: 04fb92f2f446ac54c59f45a3d1eead4f4010e702 (
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
|
.SH "EXAMPLES"
For finding out what a particular package depends on for building, you could do:
.nf
$ \fIqdepends nano\fR
app-editors/nano-2.3.2: >=sys-libs/ncurses-5.9-r1[unicode] sys-apps/file ...
.fi
This tells us that we have \fIapp-editors/nano-2.3.2\fR installed and it depends
on ncurses (among other things).
Searching for packages that actually have nano in their RDEPEND:
.nf
$ \fIqdepends -rQ nano\fR
virtual/editor-0
.fi
Tells us that \fIvirtual/editor\fR depends on nano. However, if we
wanted to know in what way a package specifically depends on another
package, one can use \fB\-v\fR.
.nf
$ \fIqdepends -vrQ logrotate\fR
sys-apps/portage-2.3.18: >=app-admin/logrotate-3.8.0
.fi
This way we can see there is a specific dependency expressed here. If
the above had used \fI<logrotate-3\fR, for example, no matches would be
returned. Not using any specifiers allows to reveal in what way a
dependency is expressed.
|
GitWeb
