Code repository: http://github.com/gweis/collective.recipe.platform
Limitations:
The recipe currently only generates platform strings for darwin10 and darwin9. Due to the simplicity of the recipe itself, it should not be hard ta add further platform-prefixes. (Patches and other contributions are welcome).
Example usage
This recipe provides a way of defining buildout variables which can be referenced form other parts with platform specific values. It does not try being intelligent and guess what values it should set, but gives the user full control, with the drawback/advantage of keeping all settings in a single or multiple configuration sections.
But examples are probably a better explanation:
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = debug
...
... [platform]
... recipe = collective.recipe.platform
... environment =
... darwin10-environment =
... CC=gcc-4.0
... flags =
... darwin9-flags =
... CPP=cpp-4.0
...
... [debug]
... recipe = zc.buildout:debug
... env = ${platform:environment}
... flags = ${platform:flags}
... plname = ${platform:platform}
... """)
Ok, we have a part called ‘debug’. This part just prints all given options to stdout. In our case it uses values referenced in the platform part.
The platform recipe looks for options starting with a platform prefix, taxes the remainder of the option name and replaces the value.
The result of a buildout running on OSX 10.6 (darwin10) is the following:
>>> print system(buildout) Installing platform. Unused options for platform: 'darwin9-flags'. Installing debug. env='\nCC=gcc-4.0' flags='' plname='darwin10' recipe='zc.buildout:debug'
Changes:
0.1 (2009-10-13)
initial release
Metadata
Release files for collective.recipe.platform 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.platform-0.1.tar.gz | 3.8 kB | Without provenance | Details for collective.recipe.platform-0.1.tar.gz |
Release files / collective.recipe.platform-0.1.tar.gz
| Download URL | collective.recipe.platform-0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2230d6538c18d2330a5d5e4a4e01cd7dafbbecdacc425f2656b78ddf6f26b3c
|
|
BLAKE2b-256 checksum How to use checksums |
038a08ce043378e3aa027f74304a6eb07a9aad6288c08168ca232950152d8b25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.platform 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.