Derek Richardson wrote:
For two different buildouts that report being Plone 3.0, I get these two
different values in the egg list in bin/instance:
.buildout/eggs/plone.recipe.zope2instance-0.6.1-py2.4.egg
.buildout/eggs/plone.recipe.zope2instance-0.7-py2.4.egg
That's the *recipe*, not the Zope version. Buildout (unless you run in
-N or -o mode) will always get the latest version from the Cheese Shop,
so if the first one was built some time ago, it may have the older recipe.
It appears to me that, though the Plone eggs are tied down, the Zope instance is
not.
It is by default, but you can override.
Should it be? It is nice if the Plone 3.0 recipe auto-gets updates to Zope
2.10.x.
It won't, it can't.
OTOH, it makes it difficult to diagnose problems if supposedly-identical
buildouts are not identical.
All the recipe behaviour is documented, btw, on the relevant Cheese Shop
pages.
Martin
--
Acquisition is a jealous mistress
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers