That's what I've been using.

Well... it seems to be an improvement. I have a piece of fairly recent coursework with heavy embedding of an OOo Draw file - with 1.9.79 (Official 2.0 Beta RC) it crashed hovering over the objects. This time, it doesn't, but still doesn't load the relevant object.

In terms of the package itself, they've added two new files:

openofficeorg-mandrake-menus
openofficeorg-freedesktop-menus

Freedesktop is almost useable, but the /usr/bin files still point to some obscure /etc/openoffice.org-$VERSION (the /etc and - are wrong, obviously) and the icons don't work with KDE.

Fiddling the SuSE package still provides the best results, and with a bit of fiddling, I suspect the menu entries will now also work with Gnome.

Also, I haven't run the configuration stuff and it appears to work fine without it. I'll keep testing and see how it goes.

Thoughts:

1) What use does 'Printer Administration' have in Slackware?
2) How does one remove anti-aliasing in Printer Admin, and change the font in the helpfiles (the menus are fine, but by default, the actual files themselves seem to use Bitstream Vera Sans, although everything else I have is set to Arial. Perhaps it uses some Gtk/Gnome specific file, such as .gtkrc?)

The following is therefore the current script I used for 1.9.91:

Edit

Latest script is here: http://www.linuxquestions.org/questi...37#post1604737

Hmm, the latest version keeps crashing on me, even when i'm not doing anything.. So i went back to 1.9.79. It seems more stable to me.

Nevertheless, i'm looking forward for the next updates.

Weird, I've had less document recoveries, none, with newer versions.

I also had problems with 1.9.91, but I installed 1.9.93 just today and it seems to be stable so far. I'll post if not.

.93???? I don't see that on any of the mirrors I looked at.

Go to this page: http://download.openoffice.org/680/index.html

Choose a mirror. Navigate up to the Parent directory, then find the 680_m93 directory.

For example, on one of the U.S. mirrors, here's the url you'll end up with:

http://bulkdownloads.digitaldistribu...loper/680_m93/

But you can find "680_m93" (=1.9.93) on any of the mirrors that have been updated today. I checked five and four had it.

Have fun.

Ha! Thanks, just didn't go to parent, then back down.

Hidden treasures ...
They're there for those who seek them.

I just noticed that OOo 1.9.95 is out.

Choose a mirror at http://download.openoffice.org/680/index.html

From the mirror site, go up to the parent directory and look for the 680_m95 directory.

I read the other day that OOo 2 final is being delayed until July or so. That suggests that the OOo people would benefit from having people test these development releases. It's not much trouble to install, and it doesn't zap your existing OOo installation.

While you're at it, you might as well delete the suse Menus too.
Btw, i can vouche that it also works for xfce too.

It does delete the SuSE menus, but it first of all converts them for use with KDE, Gnome and XFCE (the SuSE package provides icons for both KDE and Gnome/XFCE/Anything using /usr/share/applications, as the *.desktop entries do not contain a fixed address for the relevant icon), creates a new package, then deletes the old SuSE menu package.

There are a few things from investigation that I'm still not certain about:

1) Is it really necessary to have eight core packages? These could easily be folded into one (perhaps this is to allow the core packages to be split up all over the place for an installation disc, or easy download?)

2) Is the testtool package necessary? It seems to be for testing VCL - the toolkit used to build OOo.

3) A suggestion from the Fedora mailing lists - fold spellchecker into one of the core packages. Basically, in OOo this package only contains 3 files. It is only seperate for the sake of StarOffice, as that apparently uses an entirely separate Spell Checker from OOo.

4) Total side note - there's no internationalisation with these packages. It's US English only, unless you go and download the relevant stuff from elsewhere and install it yourself (rather annoying when all I want is en_GB...)

5) I haven't run any of the configuration stuff suggested at the end of this script, and I haven't had a problem. (I suspect all the Java stripping stuff from earlier is due to Debian's policy on free software, and that I understand this causes problems with shipping the Java VM with Debian?)

The following is the latest version of the script (tested against 1.9.95), which now also adds package descriptions (mostly lifted from the OOo website)

(NB: To add package descriptions *properly* is horribly complex. I did try gunzip'ing the packages, and then adding to a tar archive. Problem? All the OOo files are prefixed with ./ whilst the 'install' stuff is not. Looks good on install, but Slack strips the first two leading characters from all the files it lists in /var/log/packages to compensate. Problem - install becomes stall, and you get complaints when you try to 'removepkg.' If you prefix the install directory with ./ when trying to add it, Slack ignores it when you run installpkg.

(Solution? Extract *each* and *every* bloody package one by one, add an install directory and slack-desc, then run makepkg! Takes a while, but it does work! However, because all this time for nice descriptions is not everybodys cup of teas, if you don't want them, change yes to no here:
)

Without further adieu (and no more blood, sweat and tears... at least until tomorrow), the latest version of ooo.SlackBuild!

Edit
Latest SlackBuild is here:
http://www.linuxquestions.org/questi...37#post1604737

Excellent work! i can say it works like a charm =)

IMO, No.. its not neccessary, not even for easy download because you're download 1 big .gz with all the rpms in it anyway. If its possible to reduce them to 1 core package (or even all of OO to 1 pkg), then it might be more appropriate to do so..

Well, Some might need it, same as how some might need impress.. You could always just add an option which disables it by default, and would be enabled if anyone needs it.

1 less package in the total list

Hmm.. true.. I think i just got used to en_US in the end..

I'd say the same over here, but i'm not sure what the command really does.

An extra suggestion.. Why not have the end .tgz packages in an OO folder in the same directory we originally have the OOo_1.9.95_LinuxIntel_install.tar.gz stored in, instead of leave them in the /tmp folder?

Keep up the good work.

EDIT:
========
Hmm, for some strange reason, OO Writer no longer shows in XFCE's Office menu...
It currently has Base, calc, draw, impress, math, and printadmin, but not writer..
Yes, the package is installed.

EDIT 2
=========
hmm... few hours later and the link is back there again.. heh. Nevermind

This seems to be due to a quirk in /usr/bin/rpm2tgz, caused by this line (near the bottom):

I'm thinking that changing this to

(i.e. changing the "." to a "*") would get rpm2tgz to create tgz's without the leading "./", so they look more like packages created with makepkg.

I think Pat/whoever needs to update his script!

Nobber:
Thanks for that! I've sent an e-mail suggesting it to him (Pat's name is at the top of the rpm2tgz script). I can't see why not to use * (I did a test with ooo-calc and it converted fine), but perhaps Pat has a reason? I'll see if I get a response or not, but I'll still have to assume (for compatibility) that people have the default rpm2tgz (although the script could be updated later to take advantage for those that don't.)

Xushi:
Reducing the core packages is easy (and I wanted to do it anyway). Whilst I can fold all the packages into one big one (and I'm working on an option to do that), my personal preference is to have the core package, and then each of the applications separate - something about that just appeals to me (who knows, one day I may be struck with the urge to keep adding and removing Writer for amusement...)

A little bit of further checking - it does suprisingly have most of en_GB with it, and bits of other langauges (mostly incomplete). And adding internationalization packages is somewhat out of the scope of this script.

SlackBuild scripts dump the built package/s in /tmp by convention, so I'm just tagging along.

The same things happens here on KDE - unless I run the 'Menu Editor' and ask it to save, then voila, Writer reappears. There's nothing wrong with the link, so I can't figure out what's going on there...