You may add the following options to your install.sh command line to more finely control your installation:

--target=pathname

Use to specify top-level path for installs. Plone instances and Python will be built inside this directory.

--user=user-name

In a root install, sets the effective user for running the instance. Default is 'plone'. Ignored for non-root installs.

--with-python=/fullpathtopython2.4

If you have an already built Python that's adequate to run Zope/Plone, you may specify it here.
virtualenv will be used to create an isolated Python environment for the installation. Your system's site library will not be touched.

--password=InstancePassword

If not specified, a random password will be generated.

--nobuildout

Skip running bin/buildout. You should know what you're doing. The main use for this option is if you want to use the Unified Installer to put all the pieces together, then plug in your own buildout.cfg.

Library build control options

The Unified Installer will try and figure out whether or not you have the libz and libjpeg libraries on your system. If you do, great; if not, the installer will try to build them in the lib/ subdirectory of your installation target and link to them directly. This may not be what you want. If not, use the following command-line options to tune the behavior.

--libz=auto|global|local|no

auto

to have this program determine whether or not you need the library installed. If needed, will be installed to $PLONE_HOME. This is the default behavior.

global

to force install to /usr/local/ (requires root privileges)

local

to force install to $PLONE_HOME (or $LOCAL_HOME) for static link -- even if a system copy of the library's found.

no

to force no installation of the library.