This recipe is largely based on collective.recipe.mxodbc, a recipe created by Jarn to installed eGenix mxODBC 3.0.X. That recipe will install mxODBC 3.0 and also build an mx.base package from source. For the Zope database adapter eGenix releases prebuilt packages with mxODBC 2.1 and the Zope Database Adapter included. That’s what this recipe is for.
You can add this recipe to your buildout by adding a section like this:
[mxzopeda] recipe = collective.recipe.mxzopeda license-key = puty-ourl-icen-seco-dehe-repl-ease licsenses-archive = mxzopeda-licenses.zip
The licenses archive should be a zip file with one directory for every license you want to use with the license key as file name and the license file you got from eGenix for that code in the directory.
The recipe tries to detect the correct platform to download the prebuilt archive for, but has so far only been verified on Apple OS X universal systems and Ubuntu server 8.10 for i686. Please report any problems if you encounter problems with other architectures.
Metadata
Release files for collective.recipe.mxzopeda 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.mxzopeda-0.1.tar.gz | 4.6 kB | Without provenance | Details for collective.recipe.mxzopeda-0.1.tar.gz |
Release files / collective.recipe.mxzopeda-0.1.tar.gz
| Download URL | collective.recipe.mxzopeda-0.1.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d571452e72e88636c45f037dc8f4616d0597f95029dda82593cb104b8c6394a
|
|
BLAKE2b-256 checksum How to use checksums |
7d8e762f5482d0edc9edae7faca8031a81c23b2c2d417e9a627b8b69d8c13865
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.mxzopeda 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.