Apache OpenOffice (AOO) Bugzilla – Issue 3592
Need RPM Installation
Last modified: 2004-10-12 09:46:34 UTC
An RPM installation is a must for most Linux users. It allows easy updating and dependency checking. It also allows more interoperability between different packages. It would allow other apps to make easily make use of open office packages and allow open office to easily make use of other packages in the RPM database. RPMs are readily available for most other such projects (e.g. KDE, Galeon, Koffice, Mozilla, AbiWord, etc.). They are used as a matter of course by Red Hat and Ximian to install and upgrade all of their products. Why not for OpenOffice? P.S. And deb packages should be available for Debian, et al., as well.
Hi Falko, a new 'enhancement' for you. BTW: I can't see why this should be >P1<? It's no desaster or doesn't prevent me from working.
Since we are a platform independent program we use a proprietary installation routine (yet). We are already considering to adjust our setup program to the different OS standards (e.g. MSI). But at the very moment I cannot make any statement on this nor give any outlook. Therefore changed to "later". Stay tuned!
Created attachment 1914 [details] My RPM .spec file for OpenOffice
Created attachment 1915 [details] Oo wrapper script - Source1 for RPM
Created attachment 1916 [details] GnomeVFS config file (RPM Source2)
I'm using RPM to install OpenOffice on our network, via packages built by myself. The spec file and related sources have been attached to this report. They were originally based on data from Mandrake's source RPM for the 641 builds, but there isn't much left of that no. The RPM is currently Intel Linux only, and it's based on the binary distribution as building from source is a bit too tedious right now. Apart from that, there are two interesting features: 1. "setup" is not used once the RPM has been created - it's not even included in the distribution. Instead, a wrapper script that will create .sversionrc and the user config directory (which are the only bits that are _really_ needed) if necessary, then run the appropriate executable is used. 2. Dictionaries are installed on a shared location - /usr/share/myspell, with the appropriate links from OO install directory, and packaged in separate RPMs. This is the only way of setting everything up, I think; copying everything to the home directory of each user is simply *wrong* (and fortunately, not really necessary), and generic components like the spell checker should be kept separate from the application.
Oh, and please disregard Source10-14. These bits were moved to separate packages, but the source tags were left in by mistake. Hmm, maybe I'll attach the spec file for these packages as well...
Created attachment 1917 [details] Spec file for MySpell language packs
Created attachment 1918 [details] ispell-to-myspell affix converter (myspell.spec source 3)
Created attachment 1919 [details] myspell.spec patch0
Created attachment 1920 [details] myspell.spec patch1
Ximian is now offering an RPM-based distribution of OpenOffice 1.0, integrated into its GNOME desktop. http://www.ximian.com/about_us/press_center/press_releases/openoffice.html
How execatly is the Ximian version structured, in terms of setup handling, language support etc.? Maybe I'll download it and have a closer look... In the meantime, I've updated my own package a bit. I've worked on better integration with the rest of the system for the printer setup now. Notably, I have written a script that will create a new printers.conf based on the setup of CUPS (http://www.cups.org), and that may be used as an alternative to spadmin.
Created attachment 2067 [details] Updated .spec file
Created attachment 2068 [details] Simple script for CUPS based printer setup
CUPS support script is now replaced with a C++ program, see issue 6284.
I just thought I might update the information here in case someone decides it is now "LATER", and considers this issue again. Anyhow, Red Hat is of course also providing an OOo RPM. I'm still building my own package loosely based on the Red Hat one, though, since I want to test the various betas and prereleases. I will attach my .spec file and wrapper for 1.1rc4 shortly. Also, I'll try to make sure ftp://ftp.procaptura.com/pub/SRPMS has an updated source rpm at any given time. - The term "source" should not be taken to literally here since I merely repacakge the binary distribution. Building from scratch was a bit too painful the last time I tried...
Created attachment 9153 [details] .spec file for 1.1rc4
Created attachment 9154 [details] New wrapper script
Created attachment 10047 [details] My spec file for OOo 1.1
Created attachment 10048 [details] Wrapper updated for 1.1
Yet another version of the stuff I'm using when building RPMs. Note: 1) This entry would be a lot cleaner if you would upgrade to the current version of Bugzilla, which allows attachments to be marked as obsolete, among other things. 2) There are at least 2 other reports requesting RPM support - perhaps someone with the suffient permissions to mark as duplicates ought to clean up a bit.
*** Issue 14808 has been marked as a duplicate of this issue. ***
Current snapshots ( >m51) are RPMS.