SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
And lest you be scared by that (because OOo takes 1000GB of disk space, 12GB of RAM, and 6 days to compile) the SBo SlackBuild is one of the few that repackages the binaries for you via rpm2tgz, so it'll have you officed quickly and easily.
Wellll if you look at the script, you will find at the end it uses 'makepkg'. You can go to the build directory, delete what you don't need and run makepkg your self.
The package is most likely built in /tmp/SBo/package-openoffice.org
However, I just looked over the package and it's not that simple. Everything is crammed together. maybe in the extracted RPM there are some scripts that can help you determine that..... 433MB is quite large
This is what I use: http://slacky.eu/aadm/pkgs/index.php?ver=13&pkg=392
It's not an OOo package itself, but it downloads the official OOo RPM package for your architecture (64-bit for Slackware64 and 32-bit for Slackware), converts it to a .tgz Slackware package and installs this automatically. The only thing you are requested to do yourself, is to choose your language from a list.
Works extremely well and is the most convenient way to install non-US-English versions of OOo, I found so far.
But I Robby Workman's packages and his SlackBuild script work very well, too. For non-US-English you just have to change the file name specified in the script.
Some time ago, I tried also the package from LinuxPackages.net. I had no problems with it, too. Today I prefer the slacky.eu solution, as my language is not US-English, and because they always include a SlackBuild script (not that I needed that very often; in fact, I used to install a lot of the packages provided by Ken Zalewski on LinuxPackages.net, and never had a problem with them).