XBPS utility to generate package dot(1) graphs
|[OPTIONS] MODE PKG
TABLE OF CONTENTS
xbps-dgraph utility generates a
dot(1) graph of a specific package stored in
target root directory or in registered repositories and prints the result to
stdout. The argument PKG is a package expression, which
is explained in the PACKAGE EXPRESSION section.
A package expression is a form to match a pattern; currently xbps supports 3
ways to specify them:
- by package name, i.e: “foo”.
- by exact package name and version, i.e:
- by specifying a package name and version separated by any of the following
- < less than
- > greater than
- <= less or equal than
- >= greater or equal than
The first repository matching the package expression wins.
Only one of the following modes can be used at a time. By default and unless the
- Specifies a path to the XBPS configuration directory. If the first
character is not '/' then it's a relative path of
- Specifies a path to the graph configuration file, to modify the settings
of the generated graphs.
- Enables extra debugging shown to stderr.
- Show the help message.
- For remote repositories, the data is fetched and stored in memory for the
current operation. This ignores the existing on-disk repository archives
- Enable repository mode. This mode explicitly looks in repositories, rather
than looking in the target root directory.
- Specifies a full path for the target root directory.
- Show the version information.
-R option is specified, the target
PKG will be queried in the root directory, otherwise it
will be queried in registered repositories.
- Generates a graph configuration file in the current working
- Generates a full dependency graph of the target package.
- Generates a metadata graph of the target package.
- Overrides uname(2) machine result with
this value. Useful to install packages with a fake architecture.
- Sets the target architecture to this value. This variable differs from
XBPS_ARCH in that it allows you to install packages
partially, because configuration phase is skipped (the target binaries
might not be compatible with the native architecture).
Juan Romero Pardines <email@example.com>
Probably, but I try to make this not happen. Use it under your own
responsibility and enjoy your life.
- Default configuration directory.
- Default system configuration directory.
- Package files metadata.
- Default package database (0.38 format). Keeps track of installed packages
- Default cache directory to store downloaded binary packages.
Report bugs at https://github.com/void-linux/xbps/issues