The default installation directory is $home. If root is installing
OOo, it will be the /root directory.
Falko,
is there a chance to change this with the new setup?

Forgotten to reassign.

But what about changing it when the installation program discover 
that the user is "root" and then suggest either "/opt" or 
"/usr/local/lib"?

Before you choose either of these please look up the right directory 
in http://www.pathname.com/fhs/

Hi,

FYI, the script called "install" which is found inside the main 
installer directory after untarring is actually a wrapper for setup 
and will properly use the setup -net swicth and will properly default 
to either the /usr/local (for net installs) or the home directory 
under (single user installs).

It also understand unix command line options:

try :

./install -h

for complete syntax.

To use it to do a net install into /opt all you have to do is:

./install --prefix=/opt

For some reason the Unix "setup" instructions on the main website 
never bother to mention this script and therefore no one is using it.

I am beginning to regret I ever wrote it.

Either way, I think for the next versions of OOo (down the road) 
setup itself should handle normal command line switches (either via 
wrapper script or so better way) and handle the defaults you asked 
for (IMHO).

Thanks,

Kevin

Don't regret it at all Kevin.

I am very happy you told me about it - and I found some errors in it and even had an enhancement too:

  - Change "OpenOffice.org 1.0" to "OpenOffice.org1.0"

    At the end of the script creation of some symbolic links 
    fails because the source is wrong. The failing commands 
    looks like this if they use the default values:

      ln -s /usr/local/OpenOffice.org 1.0/<prg> /usr/local/bin/<prg>

    where <prg> is the different commands which starts the 
    different applications within OOo.
    
    The value of variable $oo_version is "OpenOffice.org 1.0" 
    but the default directory where OOo is installed is 
    "OpenOffice.org1.0" so the value of $oo_version should be 
    changed to the same.

    so change:

    oo_version="OpenOffice.org 1.0"

    to:

    oo_version="OpenOffice.org1.0"

    In the future the directory where OOo is installed should 
    be "OpenOffice.org_<version>" so it doesn't contains spaces 
    but it at the same time is more readable and nicer than 
    "OpenOffice.org<version>".
    
  - Change the installation script so it does not have to 
    run from the directory where the installation script 
    is.

    The setup command looks like this: 

      ./setup <something>

    Then the script will fail if it runs from another directory 
    than where the setup command is.

    At the top of the script the directory for the called command 
    should be sat as $called_dir and be used when the setup 
    command is called:

    called_dir=$(dirname $0)
    ..
    ..
    $called_dir/setup
    
  - Change the installation script so it does not try to 
    create three but just one symbolic link to the swriter 
    command.

    Delete the last two ln commands which try to link to 
    swriter.

You can find the diff patch at:

  http://ooo.chbs.dk/patch/install_patch

I have also tried to attach the above file but it looks like it doesn't worked.

I will use my patched install script for the Danish OOo distribution for Linux.

Hi,

Thanks for the feedback.

Yes, $oo_version should stay as is, but the symlinks *should* have 
used $oo_home and not $oo_version (please see issue 4477 for a bug 
report).  This fix has laready been commited to the OOO_STABLE_1 
tree.

Yes I hate space in directory and file names too.  The reason 
OpenOffice.org1.0 was chosen as opposed to OpenOffice.org_1.0 was 
that the current build defaults to OpenOffice.org1.0 and I wanted 
the script to match.  Perhaps it should change there as well then we 
could change both.

As for allowing the location of the script to vary, that is probably 
a good idea.  Our plan was to use a simple wrapper script that comes 
right inside the installation tarball and will handle the common 
unix command line switches.  For the future, I think the setup2 
project will be changing "setup" directly to create a similar more 
unix like interface; so the "install" wrapper was viewd by me as a 
stop-gap measure only.

BTW:

Congrats on the Danish version!

Take care,

Kevin

If I install Oo.o 1.1 it like to install itself (in case of network
installation) to /opt/openoffice.org

closed