Don't you all think it is outrageous that OpenOffice doesn't have neutral install system like previous versions did?

So what does this mean? We should all switch to RPM based distros?
What are we gonna do about it?

i spent 5 minutes and made myself a openoffice slackware package, thats what i did about it lol

Just like Bmfan and egag, I just made my own package. I found the best things was to run rpm2tgz on all the rpms, except the folder for other distros. Then I moved the resulting tgz's to another directory and did "explodepkg *" in that directory. Moved the tar's away from that folder and created one big package. Installs as one package now and I need to add items to the kde menu myself but works very well on both laptop and desktop pc. With the added bonus of only one package to remove later when the next revision comes out.

rnicolson:

The SlackBuild I produce does have a very easy toggle for building one 'super package' - my preference is simply not to, but I leave the option open to others (plus it will automatically give you proper menus for KDE and the other Freedesktop compliant DEs/WMs, such as Gnome and XFCE).

Just change the value of 'FOLDALL=no' to 'FOLDALL=yes'

titopoquito:

I noticed that the other day and thought it looked odd. I suspect I didn't copy and paste the command correctly. IIRC it was a recent addition as a concession for Gnome users.

There may be some other installation scripts that OOo tries to run, but I've found all of them to be totally unecessary.

AxeZ:

Whilst I didn't particuarly like the 1.1.x installer, something more distrbution neutral than RPM would have been preferable. Obviously, letting RPMs touch your system is not really acceptable, so rpm2tgz is the only alternative (although it's not perfect).

egag:

I don't just use rpm2tgz in isolation because aside from the packages not following the Slackware naming conventions, they don't deal with symlinks in the Slack way and this has caused me problems with removing OOo packages (symlinks are stored in the core?u RPMs, instead of being commands in doinst.sh) - so if I have to take apart and run 'makepkg' again to get a proper package, I thought I may as well throw in some slack-desc's.

Plus I don't like having to manually create my own menus every time I upgrade OOo - the SlackBuild evolved out of that as an automated way to do all of the above.

i was more or less giving a quick and dirty way to get oo installed on a Slackware system.
your script will build a real Slackware-package that can be used for installation, but also can be
used for distribution to others.

i also noticed the symlinks in the rpm packages, and " removepkg " cannot handle them.
but since all goes into /opt/openoffice.org2.0/ , uninstalling can be done by just removing that complete directory.
then i'll just have some broken symlinks that i made myself in /usr/local/bin.

...and i'm looking into your script to see how the menu-entries are made :)

egag

Not having something to create kde menu items prompted me to have a look at the how/where's of menus and icons and subsequently, because I'll be installing OOo-2.0.0 on other machines, I've
made up a slackpack for creating kde-OOo menu items.

If anyone is interested in it I'll put it on my website and post a link here.

I too created individual slack packs with rpm2tgz. I'm lazy so rather than go through the process of creating a single slackpack from all the others, I created a script that will do the whole thing plus install them for me

yip, i'm interested...

egag

Hi, I've read through this thread after being confronted with a .tar.gz full of .rpm's. I'm still not sure what my best course of action should be to install OOo2. I managed to rpm2tgz the lot of them (excluding anything in desktop-integration/) but there have been comments about installpkg'ing this not being completely kosher? I'm still relatively new to Linux in general, but I'm getting more comfortable with it every day and I'm always willing to learn about different aspects. I just don't want to do something that I can't undo... I don't have 1.1.x installed and I don't need any DE integration or anything (I'm using FVWM2 so basically everything like menus is manual anyway), what do I need to do to get OOo2 installed?

Here's a link. I just put it up. It's in the third item in the list.
http://members.optusnet.com.au/~rick...lack-help.html

It has worked for me feel free to modify etc if you can improve it.

Cheers

jnsg,

I have rpm2tgz'd all the rpm's in the RPMS directory and installed with the command installpkg ./*.tgz after cd'ing into the directory where the new slackpacks are.

I have not had any problems yet. Everything seems to work just fine.

since i use Slackware i feel free :)
thanks for the script.

egag

A nice guy has also prepared a Slack10.2 tgz for OOo2.0. You can download it at
http://www.linuxpackages.net/pkg_details.php?id=7940.

It worked painlessy for me. But no KDE icons were created (nor were supposed to be in this package).

amwink

well, i have some strange stuff to add to this mess. I did rpm2tgz then installpkg *.tgz on the resulting files. Everything is installed, only problem is that soffice script hangs for all users except root. I moved the script and set ln -s soffice.bin soffice and now regular users can run everything fine. What in the script is broken or what paths does root have/not have that break it for a normal user? I tried several things, chmod -R {username}.users, setting the path to mimic root's (set it back afterwards). I am using Slamd64, but can use slack packages built for 32bit with no problems (firefox, wine, etc). Any thoughts?

Could there be something different with your Slamd64 system compared to an x86? I've done 3 installs on slack-10.2 using rpm2tgz and installpkg with soffice then run by users without the problem you describe.

I've found with Slamd64 that sometimes you have to run "rm /tmp/OSL_PIPE*" first for OOo 2 to load.