2010/2/14 NoOp <gl...@sbcglobal.net>
> On 02/13/2010 08:46 PM, NoOp wrote:
> > On 02/13/2010 12:15 AM, M Henri Day wrote:
> >> 2010/2/13 NoOp ...
> >
> >>> Then you didn't actually uninstall 3.1, or you didn't install 3.2.
> >>> Please provide details on *exactly* what and how you installed.
> >>
> >>
> >> Here below, NoOp, the gory details :
> >>
> >> 1) Downloaded «OOo_3.2.0rc5_20100203_LinuxX86-64_install_sv_deb.tar.gz»
> >> package to my Downloads directory.
> >> 2) Opened the Synaptic package manager and uninstalled v 3.2.0rc4.
> >> 3) Extacted the contents
> >> of «OOo_3.2.0rc5_20100203_LinuxX86-64_install_sv_deb.tar.gz» to a folder
> >> called «OOO320_m12_native_packed-1_sv.9483» in my home directory.
> >> 4) Opened a terminal, cd-ed into
> ../OOO320_m12_native_packed-1_sv.9483/DEBS
> >> 5) Installed the Debs files via «sudo dpkg -i *.deb».
> >>
> >>
> >> After checking to see that the new installation was up and running, I
> went
> >> back to Synaptic and uninstalled all the «ooobasis-dev3.1...» files
> found
> >> there. Despite this, as noted above, both .odt and .doc files open in
> OOo
> >> 3.1, as do .pps files. In addition to the
> «OOO320_m12_native_packed-1_sv.9483»
> >> folder mentioned above, the earlier «OOO310_m11_native_packed-3_sv.9399»
> >> folder still is found in my home directory ; would removing the latter
> >> resolve the problem ?...
> >
> >
> > A few points:
> >
> > 1. You don't need to uninstall (U)OOo, it will reside nicely
> > side-by-side with standard OOo. There is a trick to this though... you
> > need to modify the (S)OOo file to to use an alternate profile to the
> > (U)OOo. This is what I do:
> >
> > - First set write permissions on /opt/openoffice.org3/bootstraprc
> >
> > $ sudo chmod +w /opt/openoffice.org3/program/bootstraprc
> >
> > - Modify that file to:
> > 'UserInstallation=$SYSUSERCONFIG/.openoffice.org/3'
>
> Correction:
> - Modify that file *from*:
> 'UserInstallation=$SYSUSERCONFIG/.openoffice.org/3'
> to
> 'UserInstallation=$SYSUSERCONFIG/.openoffice.org3/3'
>
NoOp, thanks for your detailed reply ! My write-protected
«/opt/openoffice.org3/program/bootstraprc» file looked like this :
[Bootstrap]
BaseInstallation=${OOO_BASE_DIR}
InstallMode=<installmode>
ProductKey=OpenOffice.org 3.2
UserInstallation=$SYSUSERCONFIG/.openoffice.org/3
[ErrorReport]
ErrorReportPort=80
ErrorReportServer=report.services.openoffice.org
I tried to use the «chmod» command you suggested above, but for some strange
reason, I couldn't get the «+w» option to take, so I decided to run «sudo
chmod 777 /opt/openoffice.org3/program/
bootstraprc» instead - an elephant gun to shoot mosquitoes, perhaps, but it
worked. When I open the file, I now see «UserInstallation=$SYSUSERCONFIG/.
openoffice.org/3/3». However, despite this change, when I click an .odt or a
.doc file, it still opens in Writer in OOo 3.1 ! A piece of information
which may or not be useful in this context is that the command which opens
OOo 3.2 is «/opt/openoffice.org3/program/soffice». Hope you can suggest a
way out - I can work around the problem easily enough, by first opening OOo
3.2 and then opening my files from within Writer, but it irritates me that I
can't change the default....
Henri
