-> could it be made to blow up? At least let buildout cry out in horror?

“I have exactly one package in my ‘eggs’ line and declare everything else (including Plone) as a dependency of that package”

-> this feels like working around buildout’s not-so-sweet spots, no? I.e. buildout.cfg is supposed to grab all the eggs you need, but sometimes it goes off the rails, so instead of letting it do its thing, you take over in your policy package.

In this case, I’d suggest you create a policy product and use that to control all your dependencies (via isntall_requires in setup.py) and configuration (via statements in configure.zcml), as well as product installation in the Plone site (via statements in metadata.xml).

These days, I have exactly one package in my ‘eggs’ line and declare everything else (including Plone) as a dependency of that package. This puts everything in one place and makes it much easier to deploy the same configuration in multiple buildouts.

Martin

So if you have “my.product” as a real package you cannot also make it a namespace.

It doesn’t blow up immediately, but as you noticed it does blow up in subtle ways later on.