> I have successfully used Plone Unified Installer to test Plone 3.0 to Plone > 3.1.5 but the sysadmin doesn't like this installer because it installs its > own python.
If your sysadmin wants to make sure that Python 2.4.x (ideally 2.4.5), along with its development headers, is available, you may use the Unified Installer with its --with-python=... flag to use the existing Python. The installer will use virtualenv to make sure that the system libraries aren't changed. > - Not all servers where you need to grab stuff from are stable or mirrored; > if a distant server goes down, your buildout may not work. If someone moves > or removes something you depended on, you may be unable to run your buildout > at all. This is annoying when it happens, but not much of a problem for production use, since you only use online resources when your adding or updating functionality. And, it's not really a problem to clean it up if buildout fails. zc.buildout is by far the best configuration management scheme we have for integrators. Steve On Tue, Nov 18, 2008 at 9:40 AM, francoise <[EMAIL PROTECTED]> wrote: > > Hello, > > My server is running a Debian distribution and I try to install Zope/Plone > on Lenny with the system adminstrator. > > I am lost because there are 3 (at least) ways of installing Zope/Plone : > > 1) Install Debian packages (the solution preferred by the sysadmin) > > aptitude install plone3_site > > 2) Create a plone3_buildout and install it with zc.buildout > > 3) Using Plone Unified Installer which generates a different buildout and > uses zc.buildout also > > I have successfully used Plone Unified Installer to test Plone 3.0 to Plone > 3.1.5 but the sysadmin doesn't like this installer because it installs its > own python. > > I saw on the faq that "Plone's "Unified Installer" installation script > compiles its own copy of Python, because many systems do not include an > appropriate version" > (http://plone.org/documentation/faq/faqsection_view?section=Installing%20Plone) > > I have noted the advantages of buildout as exposed by Martin Aspeli : > http://plone.org/documentation/tutorial/buildout/introduction > > But I found frightening drawbacks on weblion site : > - Not all servers where you need to grab stuff from are stable or mirrored; > if a distant server goes down, your buildout may not work. If someone moves > or removes something you depended on, you may be unable to run your buildout > at all. > - When your buildout doesn't completely succeed, you are (sometimes?) left > with a broken environment. > (https://weblion.psu.edu/trac/weblion/wiki/BuildOut) > > What are your experience, your feeling about those different kind of > installation (obsolete, unstable, essential ...) > > Thanks for your advice > -- > View this message in context: > http://n2.nabble.com/Which-installer-for-Plone-tp1515213p1515213.html > Sent from the Installation, Setup, Upgrades mailing list archive at > Nabble.com. > > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > -- Steve McMahon Reid-McMahon, LLC [EMAIL PROTECTED] [EMAIL PROTECTED] _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
