collective.recipe.zcml
zc.buildout recipe to create zcml slugs. Useful for example in a repoze based buildout.
Change history
0.1 (2008-07-04)
Created recipe with ZopeSkel [Stefan Eletzhofer].
Detailed Documentation
Supported options
The recipe supports the following options:
- zcml
A list of zcml entires.
format:
zcml := package ":" filename package := dottedname | dottedname "-" ( "configure" | "meta" | "overrides" )
- zope2-location
The location of the zope 2 installation.
The guts of creating ZCML slugs was ripped from plone.recipe.zope2install.
Example usage
We’ll start by creating a buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
...
... [test1]
... recipe = collective.recipe.zcml
... zope2-location=${buildout:directory}/zope
... zcml =
... my.package
... somefile:my.otherpackage
... my.thirdpackage-meta
... """)
Running the buildout gives us:
>>> print 'start', system(buildout) # doctest:+ELLIPSIS start Installing test1. While: Installing test1. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: <BLANKLINE> OSError: [Errno 2] No such file or directory: '/sample-buildout/zope/etc/package-includes' <BLANKLINE>
We need to have a valid zope installation. Let’s fake one:
>>> mkdir("zope")
>>> mkdir("zope", "etc")
>>> print 'start', system(buildout) # doctest:+ELLIPSIS
start Installing test1.
We now have a package include directory:
>>> ls("zope", "etc")
d package-includes
It does contain ZCML slugs:
>>> ls("zope", "etc", "package-includes")
- 001-my.package-configure.zcml
- 002-somefile-configure.zcml
- 003-my.thirdpackage-meta.zcml
These files contain the usual stuff:
>>> cat("zope", "etc", "package-includes", "001-my.package-configure.zcml")
<include package="my.package" file="configure.zcml" />
>>> cat("zope", "etc", "package-includes", "002-somefile-configure.zcml")
<include package="somefile" file="my.otherpackage" />
>>> cat("zope", "etc", "package-includes", "003-my.thirdpackage-meta.zcml")
<include package="my.thirdpackage" file="meta.zcml" />
That’s all.
Contributors
Stefan Eletzhofer, Author
Download
Metadata
Release files for collective.recipe.zcml 0.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 | Actions |
|---|---|---|---|---|
| collective.recipe.zcml-0.1.tar.gz | 5.7 kB | Without provenance | Details for collective.recipe.zcml-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.recipe.zcml-0.1-py2.4.egg | Legacy Egg format | - | - | Details for collective.recipe.zcml-0.1-py2.4.egg |
Total release size: 15.5 kB
Release files / collective.recipe.zcml-0.1.tar.gz
| Download URL | collective.recipe.zcml-0.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30b6c5941622ea8788716248799aa751d9abf14e7cfd6ce5df88da12e96420c7
|
|
BLAKE2b-256 checksum How to use checksums |
27ef5c2131b71354784f4076de1fda69dc108f02cabba8d051c3b021ff73cb67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.recipe.zcml-0.1-py2.4.egg
| Download URL | collective.recipe.zcml-0.1-py2.4.egg |
|---|---|
| Size | 9.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
ed434312f026560a2302c8a36050cb56563600dc4b39952e0b7a844f02213996
|
|
BLAKE2b-256 checksum How to use checksums |
44fb324a793e8bb2d856f915bf32a294314c6cd812883c160ed51eacdb585d01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.zcml 0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.