Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 02/25/2011 04:49 AM, Sigrid Carrera wrote:
Hi,

On Thu, 24 Feb 2011 12:02:07 -0800 (PST)
Bad2theBone<skotchman@gmail.com>  wrote:

What is the status of this issue? I have the same problem. I have both OOo&
LO installed but cannot install the desktop-environment rpm for redhat-menu.
What is the commands to launch each app, so for now I could manually create
menu entrees?
The usual way is using

swriter
scalc
simpress

and so on to start the individual modules. But since you have both OOo and LibO installed, you 
might want to call the app with the complete path to make sure, that the correct one starts. Once 
you've done this, you could create some aliases like owriter and lwriter to be able to 
differentiate between the two software packages.

Sigrid.


I did finally get it to install using rpm -ivh --force rpm-file-name. I saw this in another thread basically complaining about the same thing. I was not able to find an equivalent in yum as I prefer to use that. Thanks for the response. I did finally figure out the commands just the way you give them. Pretty neat how LO was able to duplicate my settings from OOo as well as my templates, so everything is there and functioning as before with OOo.

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.