Description
The buildout syseggrecipe uses system installed eggs, called syseggs. These syseggs are used instead of installing them again during buildout. This is usefull for hard to compile eggs or eggs that need specific development libraries.
Example
An example of how to use the recipe. Please note that the sysegg recipe must be the first buildout part.:
[buildout] parts = sysegg [sysegg] recipe = syseggrecipe eggs = netCDF4
To stop the buildout when not all syseggs are installed include: force-sysegg = True.:
[buildout] parts = sysegg [sysegg] recipe = syseggrecipe force-sysegg = true eggs = netCDF4
Tests
To test if all syseggs are available while force-sysegg = true is enabled in the buildout configuration.:
bin/buildout sysegg:force-sysegg=false install sysegg
Origin
This package is a fork of osc.recipe.sysegg. As such it is licensed under MIT.
CHANGES
0.1 (2013-02-05)
Patch code to allow for force-sysegg=false
Add original code from osc.recipe.sysegg.
Add buildout and setup.py.
Added readme, changes and MIT license.
3 maintainers
Metadata
3 maintainers
Release files for syseggrecipe 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 | |
|---|---|---|---|
| syseggrecipe-0.1.zip | 11.5 kB | Details |
Release files / syseggrecipe-0.1.zip
| Download URL | syseggrecipe-0.1.zip |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
549b4ea654426e6200737e9fd1ee665c89029e266c2f034ef6ec798e273a0025
|
|
BLAKE2b-256 checksum How to use checksums |
677caf354e49dbbde6f40492453b9b8a7cf637ca518d7fbf366cbc2866db88e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
