Bindep is a command-line utility for checking the presence of binary packages required by an application or library. It helps manage operating system-level package dependencies, particularly in development and CI environments, and originated from the OpenStack project to ensure necessary system packages are installed before Python dependencies. The current version is 2.14.0, requiring Python >=3.8, and it follows an irregular, as-needed release cadence.
pip install bindepVerified import paths — ran on the pinned version, not inferred.
Create a `bindep.txt` file listing binary package dependencies. Each line specifies a package name, optionally followed by profile selectors and version constraints. Then, run the `bindep` command to check for missing packages. The `--brief` option outputs only the names of missing packages.
Always use `bindep.txt` for new projects and update existing projects to use it where possible.
Ensure `bindep.txt` files are correctly formatted, adhere to Debian package naming conventions, and use lowercase characters without underscores for profile names. Validate the file rigorously.
Leverage `platform:` selectors (e.g., `[platform:debian]`, `[platform:rhel]`) in `bindep.txt` to define platform-specific package names, ensuring cross-platform compatibility. The supported platform profiles are not extensively documented, requiring some experimentation or inspection of bindep's source.
For more detailed diagnostic information, rely on `bindep`'s verbose output rather than solely the exit code when troubleshooting. Consider piping output to a file and parsing it for specific error messages.
No dependency data recorded yet.