How do I install Open Office?

Lufbery · 10-28-2006, 10:53 AM

Hi all,

I'm using a new installation of Slackware 11 with the full, default install.

I tried to install Open Office last night and it didn't work too well.

I downloaded the "Linux" package from their web site, unpacked it, and it turned out to be a bunch of RMP packages. KDE has a package manager that opened when I clicked on one of the RMPs. So I dragged the rest of them to the package manager, hit "Intsall" and ... well ... nothing really happened.

I got an error that one of the core files needed /bin/sh (which is there) and nothing else seemed to happen.

So, short question: how do I install Open Office?

I could download the source and compile it, but I think that would take quite a while on my Pentium III computer (though I'm willing to try).

Regards,

Drew

vharishankar · 10-28-2006, 10:56 AM

You could try the Slackware packages on www.linuxpackages.net

http://www.linuxpackages.net/pkg_details.php?id=7951

simcox1 · 10-28-2006, 10:59 AM

I've never actually done this, but there is a tool called 'rpm2tgz' which should convert the rpms to slackware packages, which you can then install with installpkg. Or, Slackware does come with the rpm tool so perhaps install it with that. rpm -i ***.rpm. Or use the slackware package from linuxpackages.net.

Yalla-One · 10-28-2006, 11:18 AM

I think the best way to generate the best openoffice.org is to go to slackbuilds.org and download the openoffice.org slackbuild from there.

Put it in /tmp/OOo together with the archive downloaded from openoffice.org, "su root" and then run the slackbuild (chmod 700 *SlackBuild ; ./ooo.slackbuild)

That will generate a .tgz slackbuild that you install normally using installpkg and can easily upgrade later using upgradepkg.

The builds from slackbuilds.org are high quality and extensively tested, and the best part is you can check the buildscript yourself to verify exactly what it does to your package, so you can even tweak it to your liking.
I have forinstance written a small patch to the slackbuild that replaces all the foreign language dictionaries with a Norwegian one (which does not come default with openoffice)

Good luck!

-Y1

uselpa · 10-28-2006, 12:14 PM

I too can recommend the package from linuxpackages.net. That's what I use and it works perfectly. It's also the fastest way to install OOo.

hitest · 10-28-2006, 07:37 PM

Quote:

Originally Posted by uselpa

I too can recommend the package from linuxpackages.net. That's what I use and it works perfectly. It's also the fastest way to install OOo.

I agree. I'm lazy and always download OO from linuxpackages.net. OO integrates perfectly into KDE 3.5.4.

Lufbery · 10-28-2006, 11:22 PM

Hi folks,

The build from Slackbuilds.org worked perfectly! Thanks so much for your help.

Here's a quick, newbie, question: what does the ./ do at the beginning of the build script? In other words, I made the .SlackBuild script executable, but forgot to add the ./ before it when I tried to run it the first time. It didn't run and I think I got a Bash error saying that there's no such script. But as soon as I add the ./ everything works perfectly.

I have to use the ./ before configure too when I install from source. So, what's the ./ for?

Thanks again.

Yalla-One · 10-29-2006, 02:06 AM

The ./ is to fully qualify the path of the current directory. This is normally included because it's dangerous to have the current directory (./) in path of root as you may accidentally run a dangerous program.

Imagine if you have the slackbuild in /tmp/program.slackbuild and you want to run it from root's home /root. In order to run it, you'd type /tmp/program.slackbuild, and it'd start.
Same thing for running a program in current directory. instead of /tmp/program.slackbuild, you just type ./program.slackbuild. The dot is always current directory.

-Y1

Lufbery · 10-29-2006, 01:53 PM

Thanks, Y1.

Regards,

-Drew

Randux · 01-14-2007, 07:11 AM

I was doing my own po-man's rpm2tgz script for prior releases of OO. For 2.1 rpm2tgz produces empty tarballs. I wonder if something in the rpm format they are using changed.

Anybody else experience a broken rpm2tgz or empty tarballs from these OO rpms?

duryodhan · 01-14-2007, 10:02 AM

Yeah, I tried rpm2tgz on some Oo RPMs that I had lying around. Didn't work for me either. Didn't have much time to see why etc. If you manage to get it working , tell me too!

I have FC5 installer lying arnd, which I want to use. I am on a screwed up net connection so can't download packages / Slackbuild.

Randux · 01-14-2007, 11:49 AM

It always worked fine until I installed Slackware 11.0 but the first time I tried it was with OO, so I don't know which one to blame

H_TeXMeX_H · 01-14-2007, 02:00 PM

I usually install it from the rpms, just use rpm2cpio to do it ... technically you could also use rpm2targz, but it is not as efficient (slower).

Code:

$rpm2cpio <package_name> | cpio -iv --make-directories <full-file-path>

source:http://www.linuxweblog.com/extract-rpm-files

H_TeXMeX_H · 01-14-2007, 04:25 PM

Actually, here's a script that will do it all in one step:

Code:

tempdir=/tmp/oootmp$RANDOM

if test ! $# = 2
then
	echo "Usage: `basename $0` inputfile outputdir"
	echo 'For example:' 
	echo "`basename $0` OOo_2.1.0_LinuxIntel_install_en-US.tar.gz /home/bob/Stuff"
else
	mkdir $tempdir
	tar -xzf "$1" -C $tempdir
	cd $tempdir/*/RPMS
	for i in *.rpm
	do
		rpm2cpio $i | cpio -id --quiet
	done
	mv opt "$2"
	rm -rf $tempdir
fi

exit 0

duryodhan · 01-14-2007, 11:53 PM

Thanks a lot , Tex..

Could you pls tell me wat all rpms do I need to install?
Cos I have never used Oo before.