It's here - you've got to check it out it's a brilliant tool.

1 members found this post helpful.

Really beginning to have real doubts about the value of this Slackware. Aside from the "fun" of reprogramming the software just about every time I wish to use it, there's some other "trick", which seems to be unique to Slackware, which has to be used to make the software package work. I wonder, just how far off the tried and true beaten path is this Slackware?

As for getting Slackware to work with Open Office, I've d/l the OOo software to a directory I call "Downloads". Now "Slackbuilds" is in that "Downloads" directory to. Both the OOo sofware and the Slackbuilds files have been "tar-red" and ready to go BUT the "Slackbuilds" contains ZERO instructions with regard to - how to use it? I speak English and have been doing rather well with it for years now and while that guy Vokerding and the author of "Slackbuilds" may into mind reading, I'm not and I wonder, just what else is wrong with "Slackware", that's so far off the Linux path? At this point, Slackware appears at best to be very annoying - to put it mildly.

tyc

You could always install it from source via the 'make install' method, should you choose.

0 members found this post helpful.

Perhaps it's just you? I don't have the need to "reprogram" (?) software everytime I use it. There are no "tricks" to using Slackware.

I really have no idea what you are complaining about. If you are not familiar with the use of a SlackBuild script, please read the instructions first: http://slackbuilds.org/howto/ . Using a SPEC file to build a RPM is not all that different. After all, it is just an automated way to create an installable package for your distribution.

You may conclude that Slackware is not for you. That's alright. You may also want to persevere and try to understand what you are actually doing when running a SlackBuild script. The learning experience should be satisfying.

Eric

1 members found this post helpful.

I've had Slackware before, and I had various problems. In a nutshell, Slackware is unusable for me. Mainly, both my network cards did not work

BUT, there is always a reason behind something not working. Looking for an answer without a problem is difficult. Find the problem first. MY problem with Slackware is that it had too old of a kernel. If I were not lazy, I could install Slackware and compile me a newer kernel (which has my 'drivers' built-in) and start Slackin' w/ not one problem. -- Looking at logs is a great way to start finding problems.

1 members found this post helpful.

With Slackware being the oldest still maintained linux distribution I think it's fair to say that Slackware is right in the middle of the "Linux path" whatever that means. Just because you don't know how to use something, doesn't mean it doesn't work just fine.

If you install sbopkg then it will completely automate the entire slackbuild process to the point that you don't even have to manually download the package or install it.

0 members found this post helpful.

Slackware is a vanilla Linux distro. It's more on the path than most.

0 members found this post helpful.

My point exactly.

0 members found this post helpful.

Well i think that we tried to help you so why are you upset?

0 members found this post helpful.

HOW ... DO ... YOU ... USE ... "SlackBuild"?

No instructions of any type or kind come with the program ... "un"tar it - then what?

tyc

Here's how to:
http://slackbuilds.org/howto/

You are totally lost, boy.

If you think

is a difficult "programming", you should stick up to M$. If you wanna learn, we can help you, with pleasure. But take it easy, dude. You gotta learn some linux principles before writing a very angry post. This is a very friendly forum, not a warfield.

1 members found this post helpful.

Now did you figure it out?

1 members found this post helpful.

Hang in there - it does get easier once you know where to look for info. Your easiest route is to use the package from rworkman. Open a terminal as root and type the following line:
installpkg /directory-where-package-is/package-name
then hit enter.
This will automatically install the package for you.
How to start the package will depend on what window manager you are using. In general you should be able to look in your menu and find Open Office under one of the sub-menus.

Good luck. If this doesn't work, just ask again and tell us as precisely as you can what happened. Someone will get you going.

You have nice people trying their best to help you for free.
No one made you install Slackware.
You should be more patient and be nice to these people. Actually try and solve the problem yourself instead of whining.
You should really give these guys a nice thanks.
When it comes to Linux, it all about you. You are whats responsible for anything and everything.
There is literally 100,000's of pages of documentation. It would be in best interest to consult these fine works.
I apologize for not being so helpful myself, I am not a Slackware user. My best advice is if all fails, compile the darn sucker, find the dependencies it asks for, compile it again and install it. This method is just as well documented, too.
Good luck, have fun (Linux can be if you let it), and have a glance at my sig if you are unsure.

1 members found this post helpful.