XBPS-DGRAPH(1)

πŸ“¦ version 0.60.6, in alpine 3.24, nixos 26.05, nixpkgs unstable

πŸ’… xbps-dgraph β€” the dot(1) graph maker from XBPS (yes, that's xbps-dgraph(1) from the General Commands Manual, hi bestie 🫢)

okay so picture this: you want a picture of a package's dependency drama ✨. That's literally what this icon does. The 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. Yep β€” straight to stdout, no files, no fuss, main character energy only πŸ’….

The argument PKG is a package expression, which is explained in the PACKAGE EXPRESSION section. (Spoiler: it's right below, keep reading 🌸.)


πŸŽ€ PACKAGE EXPRESSION πŸŽ€

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: β€œfoo-1.0_1”.
  • by specifying a package name and version separated by any of the following version comparators:
    • < less than
    • > greater than
    • <= less or equal than
    • >= greater or equal than

Example: β€œfoo>=2.0”.

The first repository matching the package expression wins. periodt. πŸ‘‘


✨ OPTIONS ✨

  • -C, --config _dir_ β€” Specifies a path to the XBPS configuration directory. If the first character is not '/' then it's a relative path of _rootdir_. lowkey important detail, don't skip it πŸ¦‹
  • -c, --graph-config _file_ β€” Specifies a path to the graph configuration file, to modify the settings of the generated graphs. this is where you make it pretty 🎨
  • -d, --debug β€” Enables extra debugging shown to stderr. the group chat logs of debugging, honestly πŸ’€
  • -h, --help β€” Show the help message. we love a supportive icon 🫢
  • -M, --memory-sync β€” For remote repositories, the data is fetched and stored in memory for the current operation. This ignores the existing on-disk repository archives in _rootdir_. no cap, fully in-memory brain 🧠✨
  • -R, --repository β€” Enable repository mode. This mode explicitly looks in repositories, rather than looking in the target root directory. choose your location bestie πŸ“
  • -r, --rootdir _dir_ β€” Specifies a full path for the target root directory. full path only, not vibes-based 🎯
  • -V, --version β€” Show the version information. πŸ’–

🌈 MODE 🌈

Only one of the following modes can be used at a time. By default and unless the -R option is specified, the target PKG will be queried in the root directory, otherwise it will be queried in registered repositories. pick a lane, bestie 🚦

  • -g, --gen-config β€” Generates a graph configuration file in the current working directory. a little starter kit for your graph era πŸŽ€
  • -f, --fulldeptree β€” Generates a full dependency graph of the target package. the whole tree, the entire family tree, no skipping 😭🌳
  • -m, --metadata β€” Generates a metadata graph of the target package. the lore, the details, the metadata ✨

πŸ¦‹ ENVIRONMENT πŸ¦‹

  • XBPS_ARCH β€” Overrides uname(2) machine result with this value. Useful to install packages with a fake architecture. fake it till you make it, iykyk πŸ’…
  • XBPS_TARGET_ARCH β€” 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). ⚠️ note: it's partial, and those binaries might not vibe with your native architecture, fr fr.

🌸 FILES 🌸

  • /etc/xbps.d β€” Default configuration directory.
  • /usr/share/xbps.d β€” Default system configuration directory.
  • /var/db/xbps/.<pkgname>-files.plist β€” Package files metadata.
  • /var/db/xbps/pkgdb-0.38.plist β€” Default package database (0.38 format). Keeps track of installed packages and properties.
  • /var/cache/xbps β€” Default cache directory to store downloaded binary packages.

⭐ EXIT STATUS ⭐

A descriptive error message will be printed to stderr. that's the whole section bestie, no exit codes spelled out, just vibe check failure energy πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

xbps-alternatives(1), xbps-checkvers(1), xbps-create(1), xbps-digest(1), xbps-fbulk(1), xbps-fetch(1), xbps-install(1), xbps-pkgdb(1), xbps-query(1), xbps-reconfigure(1), xbps-remove(1), xbps-rindex(1), xbps-uchroot(1), xbps-uunshare(1), xbps.d(5)

the whole friend group, honestly πŸ«‚πŸ’–


🧚 AUTHORS 🧚

Juan Romero Pardines <xtraeme@gmail.com>


πŸ™ˆ BUGS πŸ™ˆ

Probably, but I try to make this not happen. Use it under your own responsibility and enjoy your life. (iconic closing line, no notes 😭✨)

Report bugs at https://github.com/void-linux/xbps/issues β€” go snitch, kindly πŸ›πŸ”«


⚠️ real talk: this tool prints to stdout and that's it, and only one MODE at a time, bestie. don't come for me if you mash two together πŸ’…

✨ that's the whole page, ty for coming to my ted talk ✨ β€” this lil' beauty is from the Debian build, dated Feb 9, 2023, and it's the XBPS-DGRAPH(1) page from the General Commands Manual. mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from