eco wrote:
> After the positive installation of Plone 3.0 with
unified installer I want to
> create a new instance, but the installation failed.
>
> I followed the documentation
> http
://plone.org/documentation/tutorial/installing-plone-3-with-
the-unified-installer/creating-new-instances
> here
>
> and I changed the
> PLONE_HOME=/opt/Plone-3.0
>
> to
>
> PLONE_HOME=/opt/Plone-3.0/test
>
> and then, as root,
>
> ../install.sh si
>
> the output is
>
> ../install.sh: line 822:
/opt/Plone-3.0/test/Python-2.4.4/bin/python: No such
> file or directory
>
> and then many others errors "No such file or
directory".
>
> I tried with
>
> PLONE_HOME=/opt/test
>
> the result was the same.
>
> Where is my mistake?
PLONE_HOME is apparently used as a prefix for a lot of
things. It cannot
find a python in
/opt/Plone-3.0/test/Python-2.4.4/bin/python
as it is in
/opt/Plone-3.0/Python-2.4.4/bin/python
so without the 'test/' that you added.
So I guess PLONE_HOME is not the thing that you should be
changing.
Reinout
--
Reinout van Rees - Programmer at http://zestsoftware.nl/
http://vanrees.org/weblog/
mailto:reinout vanrees.org
"White space, the opposite of black hole?" --
Joris slob
_______________________________________________
Setup mailing list
Setup lists.plone.org
http://
lists.plone.org/mailman/listinfo/setup
|