Wichert Akkerman wrote: > Previously Martijn Pieters wrote: >> On 7/31/07, Wichert Akkerman <[EMAIL PROTECTED]> wrote: >>> Previously Martin Aspeli wrote: >>>> I can't see a very good reason to have a buildout inside a workingenv. >>>> Why would you want that? >>> It came up on zope-dev or zope3-dev recently and I remember thinking >>> 'this may very well be really useful'. I can't remember why though. >> I believe the advantage was that you isolate your buildout from the >> global site-packages, avoiding any side-effects of installed packages >> there. > > Ah, that sounds right. It solves the problem of doing "easy_install > i18ndude" and suddenly all your plone instances no longer working.
For i18ndude you need to use either workingenv or a separate buildout, but a combination of the two isn't needed. Only when you want to install i18ndude into a buildout which already has Zope2 or Zope3 in non-eggified form included you better use workingenv indeed. This distribution madness is the reason I don't release i18ndude as a final right now. Hanno _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
