No need to yell. Especially at people who are trying to help you. Someone already provided a link to the instructions. Did you read them? Did you even click on the link?

I actually installed OpenOffice3 using the slackbuild today, and it works just fine when you follow the instructions. Read the instructions, try them out, and come back here when you get stuck.

Yes, I clicked on the link and found no instructions of consequence ... at least which worked for me ... that's why I'm back here ... asking for the fourth or fifth time ... with all the un-tarred files in the same directory ... how do you do it?

It's beginning to look like I have a bad install. I've had that problem with Suse v10.0 which I've used for years with an older laptop and re-installing Suse v10.0 repeatedly proved to essentially be as simple as one, two, three ... With this Slackware v13, while it's supposed to be a Linux system, RPM does NOT work. I've tried converting the appropriate RPM files to *.tgz and that doesn't work. So on this end the question still stands, just how far off the "beaten path", the tried and true Linux path is this Slackware "Linux?" As seen and experienced here so far, Volkerding is actually making those Window$ people look good.

tyc

0 members found this post helpful.

Please stop feeding the troll people.

1 members found this post helpful.

its not a program its a script that needs to be runned in a terminal.
So untar the slackbulid not the openoffice binary!
then put the oo binary in the slackbuild folder.
open a terminal,become su,cd /your/path/to/theslackbuildfolder.
execute the script.
or you can use kate to make the script and pipe it to terminal or any editor of your choice.
Even cut and paste it to the terminal will do the trick or drag and drop the script,dont be afraid to try different ways to make it work for you and to understand how .sh scripts work you have to learn unix/linux
from scratch my friend.
Now if that dont work download sbopkg and use the pkgtool in terminal to install it.
then run sbopkg and its just click,click,click and you have open office installed.
Now i really hope that i didnt mess up anything here for you,im a new slackwareuser too and i had a recent mixup with the usb_modeswitch slackbuild and got help to understand how you make it work and one user rewrote and send me his script. you just cant know it all but i will tell you this,Alienbob even took time to answer your question and several other gurus and slackware developers.
You cant get that in any other dist,so be humble and wise.
And if you still cant get it to work you can email me and in worse case ill put a working openoffice on my server for you to download or send you a cd.
All im asking is that you take it easy and enjoy your new slackware,
And hey read up on unix/linux and youll be a guru in notime.

And im not being silly or patronizing here,im almost 40,swedish,and have a little issue spelling and stuff in english so you know.
I also have ADHD so im a little weird sometimes.
And if youre just trolling shame on you(and we have your ip )

AND TO THE SENIOR SLACKERS PLEASE CHECK THAT I GOT IT RIGHT.

Yes i do have a feeling you might be right but i at least tried to be a good slackwareuser

O, I have no complaints at all about the helpfulness of all the other posters in this thread! The HOWTO that people linked to as well as your and others' instructions are obviously easy to follow. That is why I am calling tyc a troll.

Eric

I appreciate your interest and input and I can tell you now ... that does NOT work. While the installed pkg is there, in /OPT, the installation is not recognized.

Again, thanks for the interest.

tyc

With the thought in mind that I have been using Linux since March of 2002, Mandrake and Suse and I can tell you now, there are indeed "tricks" to using Slackware, "tricks" that are NOT used by other distributions and Open Office is a case in point!

tyc

The only "trick" I see is that the OpenOffice.org people provide their binaries in RPM format, which is not a native Slackware package format. They apparently do not care about people who do not use RPM.

So, in order to produce a nice (de-)installable Slackware package, we use the aforementioned SlackBuild script to extract what we need from those RPMs and re-package those into a Slackware package. This is a straight-forward process, described in great detail on the HOWTO page that several people linked to.

If you are using Linux since 2002 and still have no clue what to do here, it is obvious that you have been using brain-dumbing distros all that time... all the more reason to invest a little effort and try to grasp the concept of package building.

Eric

While a hard core of Slackware devotees may not agree, I know I'm but one of many who've had problems with this distribution and yes there is a reason for the problems. One of which is a failure or outright refusal on the part of the developer to back up his work. How many years now Volkerding been "sitting" on his backside with regard to getting out that long awaited upgrade to his Slackware text?

There also appears to be a "sound problem" which I've yet to really get into -- no sound at all! And yes, I know about the Alsamixer.

Then there's the KPPP problem, one which at this point appears to a mix of Slackware and KDE issues.


Yes, I agree, there's a reason(s) for the problems and the best way I've found is to take them on, one at a time, finish it up and get on with the next one; first "A", then "B", then "C", etc.

Thanks for the interest though, it's appreciated.

tyc

0 members found this post helpful.

I'll have to look into that "sbopkg" but first I'm going to have a good look at this "Slackbuild" software. One thing I can tell you at this point is that and contrary to what one individual has stated here, RPM does NOT work when trying to install Open Office with is Slackware - and as I know and understand these things - that shouldn't be. Red Hat Package Manager as I understand it, is the defacto standard with most distributions.

tyc

What you're not aware of at this point is that which should have been a simple straight forward procedure has proven to be anything but. You wouldn't believe the HOURS lost, with just this particular issue, and yes, there are others.

tyc

You have no idea of the HOURS lost so far in this effort - no idea at all.

tyc

I appreciate the interest but experience is showing me there there's a lot more to it than what you've briefly described here ... but again, thanks for the interest.

tyc

0 members found this post helpful.

Did you install that Open Office software with Slackware v13?

If you did install that Open Office software with Slackware v13, please tell me, step by step, step by step, step by step, step by step, just how how you did it.

tyc

0 members found this post helpful.