Installing Plone 3 with the Unified Installer

The Unified Installer is a kit for installing Zope and Plone from source on most Unix-like systems, including Linux, BSD, OS X and Solaris. This tutorial introduces its use and options.

  1. What is the Unified Installer? A brief introduction to the installer, the case for using it, its options and recent changes.
  2. Root or User Install? The cases for and against installation as the root user.
  3. To ZEO or Not to Zeo? The Unified Installer will install Zope to either run in a Client/Server or stand-alone configuration. Here are the merits of each.
  4. Running the Unified Installer Preparing to run and running the Unified Installer
  5. Creating New Instances The Unified Installer may be used to create additional Zope/Plone instances.
  6. Command-Line Options Some less commonly used Unified Installer options that may still be useful to you.

All content on one page (useful for printing, presentation mode etc.)

 

Install on Solaris 10 (x86)

Posted by Michael Bobzin at Feb 15, 2008 03:12 PM
Hi,

for getting the installation done on Solaris 10 (x86) I had to
change some lines in install.sh

#!/bin/bash
...
#Build Python
...
if [ $NEED_LOCAL -eq 1 ]
then
 ...
else
    export LD_LIBRARY_PATH=/usr/local/lib
        ./configure \
                --prefix=$PY_HOME \
                --with-readline \
                --with-zlib \
                --disable-tk \
                --with-gcc="$GCC" \
                --with-cxx="$GPP"
fi

Installing on Solaris 10 (SPARC)

Posted by Joni Barnoff at Apr 05, 2008 07:31 PM
LD_LIBRARY_PATH=/usr/local/ssl/lib

This is needed to include libssl in python build

Installing on Solaris 10 (SPARC)

Posted by Jim Leek at Mar 20, 2009 04:21 PM
The main issues on Solaris are due to the fact that the installer script (install.sh) cannot always get the correct paths for the correct versions of software on Solaris. It also has problems finding the correct libraries in the Solaris environment. To add to this install.sh uses the basic Bourne shell (#!/bin/sh), which means that some of the commands which are part of the Linux Bourne shell and which are not present in the Solaris Bourne shell just do not work. Notably the -e (exists) switch is not present in the Solaris Bourne shell:

if [ -e $INSTALL_LOG ] # Does not work in Solaris.

In order to solve this do the following:

1. The locations of all dependencies need to be located on Solaris:
 (a) gcc - /usr/local/bin/gcc (gcc-3.4.6 installed from www.sunfreeware.com - default on solaris 10 is /opt/sfw/bin/gcc)
 (b) g++ - /usr/local/bin/g++ (Installed with gcc-3.4.6 - default on solaris 10 = /opt/sfw/bin/g++)
 (c) gmake - /opt/sfw/bin/gmake
 (d) gtar - /usr/sfw/bin/gtar
 (e) gzip - /usr/bin/gzip
 (f) bzip2 - /usr/bin/bzip2

In addition install.sh uses the "whoami" shell command, which on Solaris is in:

 (g) whoami - /usr/ucb/whoami

2. Ensure the above PATHs are all in the system path:

PATH=$PATH:/opt/sfw/bin:/usr/sfw/bin:/usr/ucb:/usr/ccs/bin
export PATH

(If /usr/ccs/bin is not added, the Python compile will fail with "gmake: ar: Command not found".)

3. As the -e switch is not present in the Solaris Bourne shell, install.sh and all other scripts must be changed to bash: #!/usr/bin/bash

4. install.sh uses the "which" shell command to locate the software it needs for the build. To ensure the correct versions of the software were used (rather than any Solaris defaults), install.sh was modified to explicitly set the location of each piece of software:

GCC=/usr/local/bin/gcc
GPP=/usr/local/bin/g++
GNU_MAKE=/opt/sfw/bin/gmake
GNU_TAR=/usr/sfw/bin/gtar
GUNZIP=/usr/bin/gunzip
BUNZIP2=/usr/bin/bunzip2

5. During the Python build, both the "libssl" and "readline" libraries are needed. Add them to the system library path:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/ssl/lib:/opt/sfw/lib
export LD_LIBRARY_PATH

For more info see:
http://www.eng.ox.ac.uk/Plone/solaris/plone-installation

Solaris 10 x86

Posted by Coopertino at Sep 09, 2008 02:03 PM
cat /etc/release
Solaris 10 8/07 s10x_u4wos_12b X86

The install went smoothly, after the following 2 mods :
intall.sh line 1
from #! /bin/sh --> #! /bin/bash

install.sh line 81
from GNU_TAR=`which tar` --> GNU_TAR=`which gtar`


Installation Plone-3.1.6-UnifiedInstaller

Posted by moncho at Oct 24, 2008 06:20 PM
This installer installs Python-2.4.5, and this does not work with Zope / Plone, I do not understand why using this version of python.

2.4.5 is the currently preferred python

Posted by Steve McMahon at Oct 24, 2008 06:48 PM
2.4.5 is a minor bug fix to 2.4.4. It is the preferred python for the Zope 2.10.x series.