Hi,
building lxml requires additional configuration so it finds xslt-config correctly. One possibility is to set the PATH environment variable. The other is to call setup.py --xslt-config=...
Using setup.py --xslt-config doesn't fit at all into buildout i think.
Setting environment variables before installing an egg on the other hand might be useful. Would it make sense to put this into zc.recipe.egg or would it be better to create some unrelated recipe which only sets envirionment variables?
Regards,
On Feb 11, 2008, at 9:23 AM, Christian Zagrodnick wrote:
Hi,
building lxml requires additional configuration so it finds xslt- config correctly. One possibility is to set the PATH environment variable. The other is to call setup.py --xslt-config=...
Using setup.py --xslt-config doesn't fit at all into buildout i think.
I don't agree. First, this isn't really so much about buildout as it is about the eggs recipe. The zc.recipe.egg:custom already provides custom build support. It seems reasonable to extend it to allow something like this.
Setting environment variables before installing an egg on the other hand might be useful.
Would that help in *this* case?
Would it make sense to put this into zc.recipe.egg or would it be better to create some unrelated recipe which only sets envirionment variables?
I suggest updating zc.recipe.egg:custom to accept environment- variable, assuming that setting environment variables is sufficient.
I think an option to pass setup custom options would be useful as well.
Jim
-- Jim Fulton Zope Corporation
On 2008-02-11 19:08:56 +0100, Jim Fulton jim@zope.com said:
On Feb 11, 2008, at 9:23 AM, Christian Zagrodnick wrote:
Hi,
building lxml requires additional configuration so it finds xslt- config correctly. One possibility is to set the PATH environment variable. The other is to call setup.py --xslt-config=...
Using setup.py --xslt-config doesn't fit at all into buildout i think.
I don't agree. First, this isn't really so much about buildout as it is about the eggs recipe. The zc.recipe.egg:custom already provides custom build support. It seems reasonable to extend it to allow something like this.
I would be fine with that of course.
Setting environment variables before installing an egg on the other hand might be useful.
Would that help in *this* case?
Yes, it would. Because lxml looks in the $PATH for xslt-config. So setting it correctly would help.
Would it make sense to put this into zc.recipe.egg or would it be better to create some unrelated recipe which only sets envirionment variables?
I suggest updating zc.recipe.egg:custom to accept environment- variable, assuming that setting environment variables is sufficient.
It is.
I think an option to pass setup custom options would be useful as well.
Probably. Although apparently there are not so many eggs requiring it.
Anyway, environment would be fine, option would be better :)
On 2008-02-11 19:08:56 +0100, Jim Fulton jim@zope.com said:
I suggest updating zc.recipe.egg:custom to accept environment- variable, assuming that setting environment variables is sufficient.
I added setting the environment in r84015. Jim, could you review that?
Thanks,
On 2008-02-18 11:25:03 +0100, Christian Zagrodnick cz@gocept.com said:
On 2008-02-11 19:08:56 +0100, Jim Fulton jim@zope.com said:
I suggest updating zc.recipe.egg:custom to accept environment- variable, assuming that setting environment variables is sufficient.
I added setting the environment in r84015. Jim, could you review that?
I added some fixes and did some cleanup in r84019.
Hello,
I suggest updating zc.recipe.egg:custom to accept environment- variable, assuming that setting environment variables is sufficient.
I added setting the environment in r84015. Jim, could you review that?
I added some fixes and did some cleanup in r84019.
may I poke you guys for a new release of zc.recipe.egg? :-)
-
Christian Zagrodnick -
Dorneles Treméa -
Jim Fulton