Thanks for the interest. It is appreciated but I have to ask, show me, show me exactly how you executed the script.

Keep in mind, on this end and prior to attempting to install OOo, there was nothing, nothing what-so-ever in the primary directory OPT. Volkerding appears to have re-arranged this rendition of Linux to the point where it may qualify as an entirely new OS, one which is far from the Linux mainstream.

tyc

OpenOffice.org should now be installed properly. This can be mostly automated with sbopkg which is a fantastic app, or you can do it manually for all SlackBuilds you wish to use. Same procedure as above.

It should be noted that OOo is *large* and if you run out of room on /tmp (or / if you have no separate /tmp) then the process will fail and you will either not get any package to install or get a half-functional package. Make sure you have enough room in /tmp. If you don't then you could choose another location to build in by passing the TMP variable to the SlackBuild, like so (instead of the similar line above):

You can similarly tweak other aspects of the SlackBuild. If you don't like doing this for each package then perhaps Slackware is not for you.

OOoThat is a link to OOo in a nice 32 bit Slackware package. Download it and open a terminal, cd to the loaction of that file and do: You should be good to go. The slackbuild is just as easy to do though.

Maybe Slackware just isn't for you, and no, RPM is not the standard for all distros. Just a few. There are just as many, if not more, that use .deb and in all honesty I would question anyone that has used Linux for 8 years and can't read directions, tar an archive, cp another archive, cd into a directory they just created, execute a script, and type one command.

The more I think about it, this almost seems like a practical joke. Could the OP please remove his mask?

Yeah I know what you mean... I can't even find apt-get or Yast... what a total mess... no dpkg or anything... What was he thinking!

2 members found this post helpful.

tyc, if you post exactly what is wrong and what you have tried it'd be more useful. Failures are as every bit as important as errors which are more important than just telling us it didn't work.
Remember that our attempts at help right now is closer to reverse engineering than diagnosis, since we can't understand the problems you are having.

Slackware is a Linux distribution aimed to be absolutely vanilla in every way possible. This also means the Linux kernel. A package manager is a patched and very customized spin on the Linux kernel. Slackware does not even do this. They offer Vanilla KDE, and a nice beginning selection of nice software for you to use. The point here is that Slackware is Linux. It's no custom rendition of it. While I am no large fan of Patrick Volkerding, since he has many ties to the church of the subgenius and appears to have some cult ties to many things (I am a Christian, so...), but I do not doubt the distribution itself. It's about as mainstream and on path as possible. Hence, it has a large following here at LQ.

To your problem;
Perhaps consult some documentation of the subject;
http://www.google.com/search?sourcei...fice+slackware
http://wiki.services.openoffice.org/...n_Slackware%3F
http://user.services.openoffice.org/...p?f=16&t=10667
http://user.services.openoffice.org/...hp?f=16&t=4991
http://user.services.openoffice.org/...hp?f=16&t=7567
http://www.marshalltradecorp.com/coD...are_linux.html

You can contact Sun;
http://download.openoffice.org/project/www/contact.html

Aimed for source install (2 steps);
http://wiki.services.openoffice.org/..._with_ooobuild
http://wiki.services.openoffice.org/wiki/Installing

Hopefully this will aid you.
And remember, albeit you have done your best for hours, it doesn't change the fact that we have no obligation to help you.
For instance, I have to get to school, but I stopped to type this message.

I appreciate your getting back ... and will have to try this variant of installing OOo but first I'm going to try to get it installed as suggested by the fellow in Sweeden. That there are so many different ways to install a given package isn't surprising but what does surprise me is that not one of them has worked so far - not one - including the basic RPM which others have claimed has worked for them!

Again thanks for getting back. It's appreciated.

tyc

Anyuway, thank's for getting back.

tyc

maybe you could try this one
CLICK

i tried the SlackBuilds one and it didnt work for me.. but this one worked perfectly

This thread displays a lack of the OP's basic knowledge about Linux command-line tools that is frightening :-) So this is how you end up after not using Slackware for eight years! I am not even going to try explaining the meaning of all the meticulous examples given by others which you seem not to understand. I believe it is pointless until you have learnt some basic Slackware house-keeping. Please consume the Slackware Book.

And no, "ALIEN BOB" is not a mask. My full name and contact data are present in every post I make here on LQ.

Eric

If you try to install an RPM on Slackware of course it won't work. Though Slackware technically includes the rpm app for completeness' sake, it should never be used IMO...Slackware does not use the RPM format as a standard and therefore there is no guarantee that any rpm package will work on Slackware. To assume that rpm is the standard is to ignore the rest of the Linux world. If anything .deb is the emerging standard now. Slackware has the simplest packages (.tgz), which are simply tarballs with two special files (slack-desc, which is just a description of the package in a specific format, and doinst.sh, which executes commands post-install. Usually these commands just create symlinks but occasionally there is more to it) and the actual files to be installed onto the system in a hierarchical tree. .deb files are similar but are not simple tarballs and must be extracted using other tools (for example, ar) or installed with a native package manager on Debian-based systems. .deb files are similar in that they contain control files and system files. I wish Slackware had douninst.sh or something to compare to Debian's uninstall scripts in its packages but in all they are very similar. .rpm packages are yet another variant, but in the end they're all packages with system binaries and additional distro-specific commands.

If you try to install an RPM package or a DEB package in Slackware, it will most likely fail. That is not the way to go about it, and just because you've been using RedHat-derived distros since 2002 does not mean you know the rest of the Linux world. Most software in the Linux world is compiled, so it can be made to be packaged in any format (.rpm, .deb, .tgz). SlackBuilds are simple shell scripts and nothing more. All they do is give instructions on how to compile a *specific* application and package it up into a .tgz file. You can consider them similar to an ebuild in gentoo or ports in *BSD (though most SlackBuild scripts do not automatically grab dependencies, and there is no infrastructure supported within Slackware to deal with dependencies; this is a manual task in Slackware). It is disappointing to hear that you have used Linux for 8 years but do not know bash, and I would urge you to learn it. It would certainly make using Slackware a lot easier, but it would also be very helpful in *any* Linux distribution. You don't have to use the terminal much in some other distros, but you can accomplish a lot if you know how anyway. In Slackware it is essentially a requirement to get your hands dirty once in a while. For some this is a foolish waste of time. For me, though the learning curve was steep, I spend most of my time in the terminal now; it can be made much more efficient if you know what you're doing.

Anyway, if you absolutely refuse to use (or learn to use) SlackBuilds properly, yet you still would like to use Slackware, I would point you to precompiled packages at the following locations:

Alien Bob's repository -- the prebuilt packages are in the pkg/ directory, the SlackBuilds used to create those packages are in the build/ directory for each application. Make sure you only get packages built for your version of Slackware.
Robby Workman's repository

The above are very, very reliable sources for packages. Both Alien Bob and rworkman are members of the core Slackware team, and I would trust their packages absolutely.

If you can't find what you want there, and you don't want to build with SlackBuilds at slackbuilds.org, another possible source for Slackware packages is slacky's repository. I would trust this one a little less but I have never had any problems with any SlackBuilds or packages from there (though I usually use SlackBuilds rather than packages), and they maintain a very large repository.

These resources are required for Slackware because there is no 'official' third-party package repository, unlike many other distros. This is a curse and a blessing, but Pat certainly does not have enough time to support one, and I know I dislike third-party binary packages and prefer to build from source for many reasons. slackbuilds.org is probably the most official unofficial SlackBuild resource and has SlackBuilds for many packages, and is why most people on LQ suggest using their scripts to build packages. However nothing is stopping you from writing your own SlackBuilds (which isn't too difficult if you learn bash scripting), compiling using the standard (and ugly) `./configure; make; make install` procedure and skipping SlackBuilds altogether, using src2pkg (which attempts to make nice Slackware packages from source code so you get the benefit of not having to write SlackBuild scripts while still getting a package that can be installed/upgraded/removed using Slackware's package management tools, which is much easier than maintaining old sources for each program you have installed to run `make uninstall` and pray that the uninstall rule was written correctly), or installing prebuilt binary packages. However, I would again discourage the use of packages built for *other* systems unless they are at least repackaged for Slackware. The only time I use packages meant for other distros is when the sources are unavailable and there is no SlackBuild to repackage the binaries already. I had SlackBuilds to repackage drivers for my printer, for example, which only came in precompiled .deb and .rpm packages. Again, I repackaged the drivers -- I did not attempt to hack my way through it by using `rpm` or `alien` to install them natively.

I wish you good luck. There is much to learn about Slackware and Linux in general if you are to get past your Slackware woes. In the end, if it is too much, you always have the option to use another distro. I use Slackware for a reason, but others use Ubuntu for a reason. If in the end you don't like Slackware, it would be foolish to trod on, problem after problem until you want to throw your computer out the window.

Hmm, sitting on his backside developing each rock-solid release with no corporate backing and no organized community. The nerve of the guy! Where are his priorities?

# alsaconfig

For those of you familiar with Slackware v13-64 and Open Office, see if the following install attempt and resulting display makes any sense ...

"unkown media type in type
'all/all'
'all/allfiles'
'uri/mms'
'uri/mmst'
'uri/mmsu'
'uri/pnm'
'uri/rtspt'
'uri/rtspu'
'fonts/package'
'interface/xwinamp-skin'

pakage OOo*3.1.1-Slackware menues ... installed"

A check of the primary directory OPT shows that the same two Openoffice sub-directories which were there before are there again - yet when using "x" KDE, still can not get OOo to come up.

tyc

My goodness. We need a lot more information if we are to help you at all. I have no idea *what* you did to install it and I have no idea *why* it isn't working, because I have no idea what you have done. Installing OOo 3.2.0 was dead easy for me, as it has been for every version prior to that. I used the SlackBuild but seeing as you are incapable of giving us any information as to how you arrived at your current state, my advice to you is this. Run the following command as root:

Then do EXACTLY the following. I do not want your "I haven't tried this but I did something that should have worked anyway" crap that you decided to annotate my original detailed post with. Forget SlackBuilds; neither I nor anyone else on planet Sane has the energy to talk you through that again.

All as root, please. The top two wget commands grab the actual OpenOffice package, already built for you, along with the md5sum. An md5sum is a calculated hash that allows you to verify that the download was not corrupt -- if the download was corrupt, the md5sum command will fail (and tell you so) and the package will not be installed. That complex line up there calculates the md5sum of the file (this may take a little while) and, if correct, installs the package. Otherwise it will tell you that the checksum did NOT match and it will not install the package. If this occurs, you would have to redownload the file. Do not worry about comparing the filesize of this new file to the filesize of the old file -- if the download was indeed corrupt, then it will not install anyway because the checksum will not match.

If you stray from any command I have posted and fail to follow clear instructions, I really doubt even the naive trollfeeders here will help you further.

[QUOTE=T3slider;3913698]
... I have no idea *why* it isn't working, ...
... I do not want your ... crap ...
... I really doubt even the naive trollfeeders /QUOTE]

I've seen cliques like this before, on other Linux sites (including one in which an individual from England (same goof here?) clearly attempted to give the illusion that he was God's gift to Linux. Can't remember the name of the site but if I recall correctly it no longer exists. The "clique", same as here, was composed of four or five "brave" individuals, probably juveniles or older individuals who came across as such.

While you and your associates may currently know more about Linux than I, it's clear that some of you have a hard time with human relations; you can clearly communicate better with your computers than with humans, a sign of a psychological issue or one of simple immaturity.

The uncalled for and unneeded comments as made by the few who appear to be part of the unneeded Linux clique active on this site have not helped further the Linux "Spirit" as one individual put it. If anything the juveniles in question have harmed it and have helped Micro$oft as one can only guess at the number of individuals who've turned away from this site and won't return after reading what some of you idiots have posted here ... and if I might suggest, no matter how well intended, "talking down" to people isn't the way to go about offering to help. You're not the only individual around with real Linux experience. It's a big planet.

You might also note I've posted the same series of questions on other sites and I can tell you now, my problems with Slackware v13-64 and these HP G71 machines are anything but unique. I can and do suggest that this version of Slackware may in fact be a "Linux Lemon" and it won't be the first time a money hungry merchant has foisted a defective product on the unsuspecting public.

The conduct of the few here has I suggest, deliberate or not, done harm to what Torvolds has strived to achieve and Linux as a whole would be better served were some of you to simply grow up: lead, follow or get out of the way. Irrespective of your self-proclaimed Linux "expertise" such as it is, you're doing more harm to Linux than helping it.

tyc

0 members found this post helpful.

[QUOTE=T3slider;3913698]
... I have no idea *why* it isn't working, ...
... I do not want your ... crap ...
... I really doubt even the naive trollfeeders /QUOTE]

I've seen cliques like this before, on other Linux sites (including one in which an individual from England (same goof here?) clearly attempted to give the illusion that he was God's gift to Linux. Can't remember the name of the site but if I recall correctly it no longer exists. The "clique", same as here, was composed of four or five "brave" individuals, probably juveniles or older individuals who came across as such.

While you and your associates may currently know more about Linux than I, it's clear that some of you have a hard time with human relations; you can clearly communicate better with your computers than with humans, a sign of a psychological issue or one of simple immaturity.

The uncalled for and unneeded comments as made by the few who appear to be part of the unneeded Linux clique active on this site have not helped further the Linux "Spirit" and one individual put it. If anything the juveniles in question have harmed it and have helped Micro$oft as one can only guess at the number of individuals who've turned away from this site and won't return after reading what some of you idiots have posted here ... and if I might suggest, no matter how well intended, "talking down" to people isn't the way to go about offering to help. You're not the individual with real Linux experience. It's a big planet.

You might also note I've posted the same series of questions on other sites and I can tell you now, my problems with Slackware v13-64 and these HP G71 machines are anything but unique. I can and do suggest that this version of Slackware may in fact be a "Linux Lemon" and it won't be the first time a money hungry merchant has foisted a defective product on the unsuspecting public.

The conduct of the few here has I suggest, deliberate or not, done harm to what Torvolds has strived to achieve and Linux as a whole would be better served were some of you to simply grow up: lead, follow or get out of the way. Irrespective of your self-proclaimed Linux "expertise" such as it is, you're doing more harm to Linux than helping it.

tyc

0 members found this post helpful.