anybox.recipe.sysdeps
This is a simple and stupid buildout recipe to check system requirements. It is primarily intended to check dependencies on Linux and MacOsX but any help to make it work on Windows will be integrated.
Recipe options:
deps: list all the required system package names and the corresponding command line to check the requirement.
Example buildout:
[buildout]
parts = sysdeps
[sysdeps]
recipe = anybox.recipe.sysdeps
deps = PostgreSQL: which pg_dump
Redis: which redis-server
php5-mysql: dpkg -l php5-mysql
If redis-server is not available, you will get an error while running the buildout, telling you to install Redis. You can use any command line to check whether the package is installed or not.
Contribute
The primary branch is here:
Code repository: https://bitbucket.org/anybox/anybox.recipe.sysdeps/
Changes
0.5 (12-01-2014)
small relative import fix
works on python 3
0.4 (01-07-2012)
Dependency checking is now just a command line to run
0.3 (19-12-2011)
Moved to mercurial
(bug) return an iterable instead of None
0.2 (15-10-2011)
Fixed install recipe and forgotten file
0.1 (06-08-2011)
Initial naive implementation using ‘which’
Release files for anybox.recipe.sysdeps 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| anybox.recipe.sysdeps-0.5.tar.gz | 2.8 kB | Without provenance | Details |
Release files / anybox.recipe.sysdeps-0.5.tar.gz
| Download URL | anybox.recipe.sysdeps-0.5.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3612d8fbcd1bc598477dcf503a402b31ffc3762ee5c623aba10b76e1037e74b4
|
|
BLAKE2b-256 checksum How to use checksums |
86e37c5311233a33b3f2f1c4a344d2aa4e37f0286a5f0c8bbf8f25d71697df7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for anybox.recipe.sysdeps 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
