You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've come to needing to customise my environment ($PATH specifically) when installing uWSGI such that it is able to locate a custom installed version of libxml2 (installed via Buildout) and build against that. This is somewhat easily solved by setting the $PATH either before running Buildout (or using collective.recipe.environment) - thought not easily reproducible or necessarily easily managed.
This lead me to thinking about the potential of having this recipe leverage another that can offload the downloading, configuring and installing uWSGI. buildout.recipe.uwsgi is effectively doing cmmi, so my thinking behind this is to reduce code duplication (downloading/extraction/compilation/removal done already), and inline with my actual issue, allow full configuration of the build process. For instance, extending off https://pypi.python.org/pypi/hexagonit.recipe.cmmi#supported-options would give environment as an option, and many others, allowing for fine grained control over how uWSGI gets built. There are other cmmi recipes out there too, but that one seemed to be one of the most featureful/active at present.
Thoughts?
The text was updated successfully, but these errors were encountered:
Sorry for the late reply, I don't have so much free time lately :( Your idea sounds interesting, but I can't help thinking that using cmmi might be a bit overkill...Anyway, could you provide me with an example of another recipe using cmmi to see how that would look like ?
I've a very similar problem. I like to compile uwsgi with a specific python-version but the Makefile og uwsgi is only dealing with "python". I've send a pull-request to ubit that solves this fact unbit/uwsgi#426 Maybe we can find together a solution, when this is merged!?
I've come to needing to customise my environment ($PATH specifically) when installing uWSGI such that it is able to locate a custom installed version of libxml2 (installed via Buildout) and build against that. This is somewhat easily solved by setting the $PATH either before running Buildout (or using
collective.recipe.environment
) - thought not easily reproducible or necessarily easily managed.This lead me to thinking about the potential of having this recipe leverage another that can offload the downloading, configuring and installing uWSGI.
buildout.recipe.uwsgi
is effectively doingcmmi
, so my thinking behind this is to reduce code duplication (downloading/extraction/compilation/removal done already), and inline with my actual issue, allow full configuration of the build process. For instance, extending off https://pypi.python.org/pypi/hexagonit.recipe.cmmi#supported-options would giveenvironment
as an option, and many others, allowing for fine grained control over how uWSGI gets built. There are othercmmi
recipes out there too, but that one seemed to be one of the most featureful/active at present.Thoughts?
The text was updated successfully, but these errors were encountered: