> * plone_devstart serves as a development start-up buildout, but eventually >> these changed should be merged to unified installer so that no separate >> "installer" for developers are needed. Even in the worst case we should ask >> people to run "cp development.cfg buildout.cfg" or similar. I don't see we >> have other barries besides by simply making the default buildout runnable >> without virtualenv (buildout is broken...). We know what must be done to >> accomplish this. >> > > We had that debate in the other thread, but there are other environment > issues that trip people up (e.g. wrong Python, missing libraries) that we > need to check too. Maybe buildout could check those (from an extension) of > course. >
We have an Unified Installer to take care of those issues and deploy a working Python environment. If the installer doesn't care of those issues then it is not working. -Mikko -- Mikko Ohtamaa http://opensourcehacker.com http://twitter.com/moo9000
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
