Introduction
The plone.recipe.command buildout recipe allows you to run a command when a buildout part is installed or updated. It is very easy to use:
[buildout] parts = command [command] recipe = plone.recipe.command command = cat README.txt
This configures a buildout part called command which lists the contents of README.txt when it is installed.
Reference
Unless otherwise specified all commands are run in the directory in which buildout is invoked. Commands have to be present in the PATH or be specified using an absolute pathname.
The following options are supported:
- command
Command to run when the buildout part is installed.
- update-command
Command to run when the buildout part is updated. This happens when buildout is run but the configuration for this buildout part has not changed.
- location
A list of filesystem paths that buildout should consider as being managed by this buildout part. These will be removed when buildout (re)installs or removes this part.
- stop-on-error
When yes, on or true, buildout will stop if the command ends with a non zero exit code.
Changes
1.1 - 2010-02-25
Added stop-on-error option to stop buildout on non zero return code of the command. [fschulze]
Use subprocess instead of os.system. [fschulze]
1.0 - 2007-09-14
Initial release.
Release files for plone.recipe.command 1.1
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 | |
|---|---|---|---|---|
| plone.recipe.command-1.1.zip | 6.6 kB | Without provenance | Details |
Release files / plone.recipe.command-1.1.zip
| Download URL | plone.recipe.command-1.1.zip |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18871d87255de65f8d179e82c842e50504502a20e3ad8c24a60467b65c371f5b
|
|
BLAKE2b-256 checksum How to use checksums |
c56db0751ece698a27b2dfe5599aee4b202a56a414593ef0c072d1ba302d3c4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.recipe.command 1.1
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.
