Hi,
I just pushed an even simpler test case that shows the defect:
https://github.com/lelit/buildout/commit/1dc3d6af0b6326500ad72798352dd1537364b5ac
that hopefully will help spotting the bug (or maybe my bad usage of the
extends functionality :-)
I already tried to tweak the
Alex Clark acl...@aclark.net writes:
Did zc.buildout 1.6.3 help at all?
No, it exhibits the very same behaviour as described in my previous
post, that is, the configuration bits from proj2 clobber those coming
from proj1. While it's enterely possible I'm misusing the extends
functionality, it
On 2012-09-05 09:55:52 +, Lele Gaifax said:
Lele Gaifax l...@metapensiero.it writes:
can you provide an example that would illustrate the problem? The file
you submitted fails because projects do not include setup.py. I would
advise to use zc.buildout 1.6.0 and see if issue persists.
Lele Gaifax l...@metapensiero.it writes:
can you provide an example that would illustrate the problem? The file
you submitted fails because projects do not include setup.py. I would
advise to use zc.buildout 1.6.0 and see if issue persists.
Sure, I added minimalistic setup.py to both
can you provide an example that would illustrate the problem? The file
you submitted fails because projects do not include setup.py. I would
advise to use zc.buildout 1.6.0 and see if issue persists.
Sure, I added minimalistic setup.py to both subprojects:
Hi all,
I'm trying to setup a modular buildout configuration, but I'm hitting my
head on an invisible wall...
Basically, I'd like to have a top-level buildout.cfg that collects
settings from various subprojects; in particular, each subproject may
augment a set of eggs, some of which may be
