[SOLVED] Apache OpenOffice 3.4.x: Anybody Have a SlackBuild For It?

tronayne · 11-28-2012, 09:11 AM

I've downloaded the stable version of OpenOffice, Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz and kinda-sorta got an idea of how to install it from a link at http://wiki.openoffice.org/wiki/Docu...n_Slackware%3F (which is talking about OO 2.0), describing using rpm2tgz (which I've never used before).

I have OO 3.3.0 installed from the SlackBuild at SlackBuilds.org, kind of doubt that'll work (but haven't dug into yet to see but kinda doubt that it will).

The instructions from Apache's wiki are:

Quote:

Installing from Linux RPMs

1. Download Ooo_2.0.xxx_Linux<NeededCPUArchitecture>_install.tar.gz.
2. Unpack downloaded .tar.gz archive, for example with command 'tar xvzf'
3. cd into RPMS subfolder, which will be created after unpacking the .tar.gz
4. Run su (or sudo -s, if your system uses sudo and you are allowed to run a shell as root with sudo -s).
5. Delete any openoffice.org*menus*.rpm files that do not apply to your system. For example openoffice.org-debian-menus*.rpm is not for Slackware.
6. Install the rpm2tgz utility, if it is missing, for converting RPM packages to native Slackware packages (.tgz).
7. Running rpm2tgz produces a .tgz file which can be installed using the installpkg or pkgtool utility.
8. Install .tgz packages with either command installpkg or pkgtool. For example,

installpkg openoffice.org-base-2.0.0-1.i586.tgz.

Repeat as necessary to install all the packages.
9. Use rpm2tgz to convert the desktop integration package and install.
10. Optionally install java runtime environment (j2re).
11. Install any language packs needed for OpenOffice.org (also converted to .tgz format with rpm2tgz utility)
12. Exit from administrator (root) shell with command 'exit'
13. Now you can run OpenOffice with the command /opt/openoffice.org2.0/program/soffice.

Note: Please check paths, permissions and users when using rpm2tgz.

Any hints?

sardinha · 11-28-2012, 10:43 AM

You can download from microlinux (owned by kikinovak):

http://www.microlinux.fr/slackware/1...ce/openoffice/
http://www.microlinux.fr/slackware/1...fice-langpack/

tronayne · 11-28-2012, 03:38 PM

Thank you! Did that. Edited the SlackBuild for version. Built it. Installed it with

Code:

upgradepkg openoffice.org-3.3.0_en_US-x86_64-2_SBo%openoffice-3.4.1_en_US-x86_64-1_microlinux.tgz

Appears to be working just fine (existing OO templates included).

Thanks also to Niki Kovacs for doing the work.

kikinovak · 11-28-2012, 03:52 PM

Quote:

Originally Posted by tronayne

Thank you! Did that. Edited the SlackBuild for version. Built it. Installed it with

Code:

upgradepkg openoffice.org-3.3.0_en_US-x86_64-2_SBo%openoffice-3.4.1_en_US-x86_64-1_microlinux.tgz

Appears to be working just fine (existing OO templates included).

Thanks also to Niki Kovacs for doing the work.

You're welcome. I'm glad my scripts can be useful. BTW, You'll also find the corresponding packages on the same server, built on 14.0, for 32-bit and 64-bit.

D1ver · 11-28-2012, 06:56 PM

Any advantage using the Apache OO verses the latest versions of Libreoffice?

tronayne · 11-29-2012, 07:47 AM

Quote:

Originally Posted by D1ver

Any advantage using the Apache OO verses the latest versions of Libreoffice?

When the great dissolution occurred (that would be when Oracle bought Sun and started fiddling with things), as I understand it, the OO developers spun off and created LibreOffice -- at that time, LO and OO were identical. After a couple of updates the template I rely on wouldn't work in LO anymore (those would be the Sun packs that I got comfortable with and, most importantly to me, did what I wanted to do). So, I went back to OO. Essentially I don't have the time or the expertise to fiddle with templates, I'm spoiled.

When Oracle gave OO to Apache things started happening and more useful templates got added (I think they also got added to LO) and life has gone on; but, I stuck with OO (worked fine) simply, I think, because of Apache (who, you know, do some pretty impressive software). I'm kind of hoping that the LO developers and Apache figure out a way to work together and combine what sure looks like the same product with slightly different bells and whistles into one. And kick Microcrap's butt into the Pacific while they're at it; hey, a guy can dream.

Any particular advantage? Well, not really. I like OO, I liked LO. Long term I think the advantage goes to Apache and, of course, I could be dead wrong about that.

OO does everything I want done, think I'll stick with it.

Hope this helps some.

jtsn · 11-29-2012, 08:41 AM

Quote:

Originally Posted by D1ver

Any advantage using the Apache OO verses the latest versions of Libreoffice?

OOo works well for me, so no need for a switch. If it ain't broke, don't fix it.

bormant · 11-29-2012, 01:13 PM

Transforming OOo-3.3.0 is quite simple:

Code:

# mkdir ~/bld; cd ~/bld
# wget http://slackbuilds.org/slackbuilds/13.37/office/openoffice.org.tar.gz
# tar xf openoffice.org.tar.gz
# cd openoffice.org
# wget http://sourceforge.net/projects/openofficeorg.mirror/files/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86_install-rpm_en-US.tar.gz

# sed -i openoffice.org.SlackBuild \
-e 's/TARNAME="OOo_/TARNAME="Apache_OpenOffice_incubating_/' \
-e 's/${WJRE:-yes}/${WJRE:-no}/' \
-e 's/basis3\.2/basis${SRCSHORT}/' \
-e 's|\*LICENSE\* readmes|share/readme|' \
-e 's/${VERSION:-3\.3\.0}/${VERSION:-3.4.1}/' \
-e 's/${BUILD:-2}/${BUILD:-1}/'

# ./*Build
# rm -rf /tmp/SBo/package-openoffice.org /tmp/SBo/en-US

# upgradepkg --install-new /tmp/openoffice.org-3.4.1-*t?z

For x86-64 use

Code:

# wget http://sourceforge.net/projects/openofficeorg.mirror/files/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz

For localized build use, for ex.

Code:

# wget http://sourceforge.net/projects/openofficeorg.mirror/files/localized/ru/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86_install-rpm_ru.tar.gz
...
# OOLANG=ru ./*Build

kikinovak · 11-29-2012, 01:32 PM

Quote:

Originally Posted by D1ver

Any advantage using the Apache OO verses the latest versions of Libreoffice?

I've tested early versions of Libre Office, and they had bugs that Open Office didn't have. Maybe more recent versions got that fixed, but there's another factor.

Since I do rely on Linux for my business, I hate the hassle of being confronted with frantic release cycles. So for mere reasons of perennity, I prefer Xfce over KDE, Firefox ESR over Firefox, Open Office over Libre Office, Slackware over Fedora.

D1ver · 11-29-2012, 04:14 PM

Quote:

Originally Posted by tronayne

I'm kind of hoping that the LO developers and Apache figure out a way to work together and combine what sure looks like the same product with slightly different bells and whistles into one. And kick Microcrap's butt into the Pacific while they're at it; hey, a guy can dream.

I'd really like to see something similar. I use 'office' applications pretty sparingly, but when I do use them the biggest problem is compatibility with MS doc/docx files. I've just stuck with what seems to have the most traction in the OSS world, which seems to be libre atm. Though with the 'openoffice' brand recognition and apache's backing It'd be nice to see everything merged back into one project..

tronayne · 11-30-2012, 06:46 AM

Though the convoluted life of OpenOffice: stating as a project by a German company, released as StarOffice -- at a price for Sun servers among others -- bought by Sun and turned into a give-away that migrated into an open source project initially supported by Sun with others joining in, Sun bought by Oracle to the horror of OO developers and the spin-off into LibreOffice. Lordy, lordy, lordy. Scott McNealy needed an "office" offering to help sell Sun servers and work stations (it used to be installable as "network" with a small run-time on an individual Sun work station or full-boat on a work station; kinda nice). I do wish that everybody would get their act together, settle any differences and present a united front at the benefit to all; heck, they're both FOSS, Wossamotta U, eh?

I have, however turned up one little minor problem with 3.4.1: I noticed yesterday that a processor was going 100% (then the other one and back and forth). Turned out it was soffice running like mad (killed it, that stopped it). I had been using it hours earlier (I launch soffice from a screen icon and the install puts a "QuickStater" on the task bar). I keep GKrellM running and I'd have seen the CPU's going nuts but didn't notice anything until, as indicated, some hours after closing OO.

I was rebuilding all the required libraries and stuff for MySQL WorkBench (had all that in 13.37, additional and newer versions, bring it up to date) and installing phpMyAdmin and I would have noticed full-blast CPUs. Doubt that had anything to do with anything but...

Anyway, I'm a happy camper with OpenOffice and, again, am grateful to Niki Kovacs.

Oh, yeah, Wossamotta U? You younger folks see http://en.wikipedia.org/wiki/Wossamo...28story_arc%29, you older guys will already know.