Dependencies

From GoboLinux Knowledge Base

Queries dependencies in a GoboLinux package. It scans the files from a program and verifies the relations to other files through dynamic linking (using the program ldd). This way, it can identify dependency relations between packages.

Contents 1 Usage 1.1 Options 1.2 Notes 2 Configuring Dependencies 2.1 Dependencies.blacklist 2.1.1 An Dependencies.blacklist example

[edit] Usage

Usage: Dependencies { [-c] <package> [<version>] | -f <file> }

[edit] Options

Options:

• -h, --help
  Shows this help.
• -v, --version
  Show program version.
• -V, --verbose
  Enable verbose mode.
• -f, --file
  Show dependencies of one file only.
• -c, --check
  Check the package's dependency file, instead of generating one.
• -r, --reverse
  Reverse dependency checking: indicate which programs depend on the given program (version is taken into account if given)
• -a, --all
  Inspect all files, not only those in 'bin', 'sbin' and 'lib'.
• -m, --missing-only
  Display missing dependencies only. (check mode only)
• -H, --higher-or-missing-only
  Display missing dependencies or higher versions only. (check mode only)
• -l, --list
  List dependency file, if any (generate if not present).
• -d, --dependencies-file
  Do not look at parses the passed file.
• -e, --execute <entry>
  Execute the command on each missing/higher. (check mode only)
• -b, --batch
  Batch mode: avoid asking questions.
• -p, --programs <entry>
  <dir> to check dependencies against.
• -w, --write
  Write dependencies to Resources/Dependencies.
• -k, --keep-going
  Don't quit immediately if any executed program fails (check execute mode only).

[edit] Notes

If no version is specified, Current is assumed.

[edit] Configuring Dependencies

Today there are many programs implementing a given feature in different ways. One such example is the OpenGL API, with implementations floating in packages such as Xorg, MesaLib and Nvidia. However, not every user owns a Nvidia card, and here comes a problem: how should one mask Nvidia from the automated Dependencies list generated after creating a recipe? This problem is now fixed with a configurable file called Dependencies.blacklist.

[edit] Dependencies.blacklist

This file allows one to specify packages that should not appear in the Dependencies file after creating a new recipe. Its format is pretty simple: one package per line, without the need to specify its version.

[edit] An Dependencies.blacklist example

The following example blacklists the packages Glibc and Nvidia. Comments and blank lines are ignored by the parser, so it's ok to include them.

# Dependencies.blacklist is documented in detail at
#  http://wiki.gobolinux.org/Dependencies

Glibc
Nvidia