I just torrented Open Office.org 3.0 but am confused on what to do with the files that came with it. I read the readme to see if there were install instructions but there wasn't anything to speak of in the readme. All I see in the OOo folder is "licenses" "RPMs" "readmes" and a file called "update". I am familiar with installing from source with make and such but I don't know what to do with these rpms....aren't these red hat files? Anyways, I would appreciate it greatly if someone could help me out

Here's a few links that will enable you to install OO 3.0. I like using Robby's package for OO 3.0.1.

http://slackbuilds.org/repository/12...penoffice.org/

http://rlworkman.net/pkgs/

1 members found this post helpful.

check this out http://www.slackbuilds.org/repositor...penoffice.org/

Hi!
I´ve had the same problem. I followed this HOWTO:

http://www.howledge.com/index.php?ac...d=2&artlang=en

It worked for me too. I´m using Slackware 12.2 and Open office 3.0.

Thanks al2,

I tried following the same HOWTO with Slackware 13 and Open Office 3.0

(note the HOWTO says to use /opt/openoffice.org2.0/program/soffice to launch, but under Open Office 3 it's /opt/openoffice.org3/program/soffice)

The install went flawlessly, but when I launch, it stops, complaining that it can't find libsfxli.so

Does anyone have any ideas about this?

Download this:
http://www.linuxpackages.net/redirec...-i686-1gds.tgz

then type:
# installpkg openoffice.org-bg-3.0.1-i686-1gds.tgz

You are done.

Why not use the SlackBuild script available on www.slackbuilds.org?

SlackBuilds are scripts that are used to create Slackware packages. To use them, refer to the howto. Once the package is created, it's a simple as:

installing this package should give you an openoffice 3.1.1 .txz in your language

if you have any problems you can report 'em to the author of the script (submax) here
http://www.slacky.eu/forum/viewtopic.php?f=4&t=22151

gegechris99: "Why not use the SlackBuild script available on www.slackbuilds.org?"


Because that would be the easy way ;-)

No, this rinky little laptop I'm using doesn't have a network connection. I have to 'sneaker-net' everything over to it.

I tried both the scripts by Robby Workman and submax. Both worked perfectly for me. For non-English installations, however, the mulitlanguage autobuilder script from submax is even more comfortable, as it just asks your for the language you desire, and then automatically downloads and installs the correct package for your architecture (yes, it detects, if you are on Slackware or on Slackware64).

With Robby Workman's script you have to download the correct package yourself, modify the package name in the SlackBuild script, then start the conversion from RPM to .t?z, and finally install the package by yourself. If you want the US-en version, it's two steps less, but for non-English versions I find the solution found by submax a little more convenient.

Both scripts work well, and both authors are very helpful and friendly to users.

gargamel