Code repository: http://svn.plone.org/svn/collective/buildout/collective.recipe.bootstrap/
Questions and comments: aclark@aclark.net
Report bugs: aclark@aclark.net
Introduction
This recipe satisfies the (perhaps not-so-common) use case of “I want to keep my buildout bootstrap.py file up to date without having to manually download it from svn.zope.org.” It also makes it possible to add a bootstrap.py file to a buildout created via buildout init. In other words, with this recipe you can avoid having to do:
% svn cat svn://svn.zope.org/repos/main/zc.buildout/trunk/bootstrap/bootstrap.py > bootstrap.py
Just add a new section, then refer to it in your buildout section’s parts. E.g.:
[buildout]
parts =
...
bootstrap
[bootstrap]
recipe = collective.recipe.bootstrap
Now whenever you run buildout, this recipe will update your bootstrap.py file.
Contributors
Alex Clark, Author [aclark]
Changes
1.0 (2009-12-19)
Clean up docs [aclark]
0.1 (2009-08-07)
Add initial functionality [aclark]
Created recipe with ZopeSkel [aclark]
1 maintainer
Metadata
1 maintainer
Release files for collective.recipe.bootstrap 1.0
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 | |
|---|---|---|---|---|
| collective.recipe.bootstrap-1.0.zip | 10.5 kB | Without provenance | Details |
Release files / collective.recipe.bootstrap-1.0.zip
| Download URL | collective.recipe.bootstrap-1.0.zip |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38a92011cc661eb5198ef08d8b97e9ff33dc7e954c6a91f6e62e1914b2e8f480
|
|
BLAKE2b-256 checksum How to use checksums |
3f69760c45fd8c519d8a3515219117abaf40bfd70a1c81161cfc0e514221137c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.bootstrap 1.0
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.
