SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I might be a bit slow on the uptake, but I've just discovered that there's a "new" fork of OO.o out in the wild, Go-oo.
Not really that new...
Quote:
Before downloading and installing the latest OO.o (3.0.1), I'd like to hear if anybody here have any experiences with the new OO player?
Well, if you mean by "new OO player", Go-oo, anyone who uses SuSE for example (that'll be me then). Seems to work. Can't really compare the two as I haven't done any benchmarking, but SuSE's OO looks better than kubuntu's OO, but then that's often the case with kde comparisons under SuSE and Kubuntu (so I don't know whether that's strictly due to the Go-OO part of the comparison).
I use GO-OO, and it's significantly faster than regular openoffice, you can also open the evil OpenXML format, and it has 3D rendering speedups. It also crashes somewhat less.
I have it installed on slamd64, not really Slackware, but I also have a slackware machine with it, and it works fine on there. I installed it locally, so I wouldn't know how to integrate it properly.
for i in *.rpm
do
rpm2cpio $i | cpio -id --quiet
done
5)
Global install:
This will result in an 'opt' directory. You can now make a new directory, move 'opt' into there, then run 'makepkg go-oo-2.0.tgz' (or similar) inside that new directory to make an installable package. 'installpkg' the package.
Or you may be able to put the rpms in a tgz and use a Slackbuild as they have the same titles as openoffice ones. These rpms would have to be in an RPMS subdirectory.
Local install:
Copy the 'opt' directory somewhere stable and symlink 'soffice' into your PATH.
Last edited by H_TeXMeX_H; 01-29-2009 at 01:56 PM.
Reason: removed unneccesary ./
Thanks for the howto, I'm going to have a bash at modifying the OO.org Slackbuild for this. Just a quick question first - won't a non-KDE user also need the freedesktop package?
Thanks for the howto, I'm going to have a bash at modifying the OO.org Slackbuild for this. Just a quick question first - won't a non-KDE user also need the freedesktop package?
for i in *.rpm
do
rpm2cpio $i | cpio -id --quiet
done
5)
Global install:
This will result in an 'opt' directory. You can now make a new directory, move 'opt' into there, then run 'makepkg go-oo-2.0.tgz' (or similar) inside that new directory to make an installable package. 'installpkg' the package.
Or you may be able to put the rpms in a tgz and use a Slackbuild as they have the same titles as openoffice ones. These rpms would have to be in an RPMS subdirectory.
Local install:
Copy the 'opt' directory somewhere stable and symlink 'soffice' into your PATH.
Good Morning,
Thought I would give it a go with the latest version, 3.1.1, so I made the appropriate changes to the text file and ran "wget ...." and that ran well, no problems
.
Ditto the second step and the "opt" directory was created.
I then made a directory, in this case, go-ootwo and moved the new opt directory to it. However, when I ran 'makepkg go-oo-3.1.1.tgz' it returned the error message, "ERROR: Can't make output package in current directory."
So where do I go next? I'll try and make another folder and direct the make package to it and see what happens.
Thanks.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by speccy
try:
Thanks. That did it. I tried variations on that theme, but didn't hit the correct combination. Again, Thanks.
BTW, Go-OO is faster and "smoother" than the "original" OpenOffice.
I did have to manually add it to the KDE menu.
"They" claim it is suppose to bit more "multi-media friendly," so I was hoping it would do a better job of playing the sound files in pps/ppt slideshows, but that was not the case, unfortunately.
Last edited by cwizardone; 09-20-2009 at 09:13 PM.
Reason: Typo.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
FYI:
Just for chuckles I removed the go-oo package, downloaded the freedesktop menus file mentioned by Eternal Newbie, added it to the list, and rebuilt and installed the new package. This time the menus were automatically created.
Thanks H_TexMex_H, External Newbie, Speccy, and everyone in this thread!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.