Benoît Bryon

Important note: the feature seems to introduce notable changes, and could be considered as backward incompatible. As an example, I had to adapt the doctests because the "multiple inheritance" behaviour...

@claytron I feel the current behaviour is "magic" too ;) In your example, you don't tell base2.cfg to extend base1.cfg. If you want to get "parts = base2 foo" where...

@mgedmin > Can't you get what you want by saying parts += base2 in base2.cfg? No. As told at https://bugs.launchpad.net/zc.buildout/+bug/1060236 : - += doesn't give the expected result. This may...

Here is another use-case example. I feel it's closer to real life: ``` .. code-block:: cfg :filename: buildout.cfg [buildout] extends = versions.cfg frontend.cfg backend.cfg .. code-block:: cfg :filename: versions.cfg [buildout]...

Updated the pull-request branch so that it remains fast-forward.

> Would this approach work for you? Yes, it works. But, I still don't find the buildout inheritance mechanism comprehensive. That said, I understand the solution proposed in this pull-request...

> That said, I guess this is not in the scope of this pull request. > So, perhaps I'd better close this thread and open another about "bases shouldn't extend...

A note about my personal status on this ticket... **Short version:** I am no longer planning to work on this story, so **feel free to take over it.** **Long version:**...

Added expectations in ticket's description.

See also #15