Ok, this is an ebuild for Openoffice 1.9 m69. It works, but there are a few catches I must add. #1. It has a fetch restriction.. so you gotta get the file yourself offa http://download.openoffice.org/680/index.html. I think it can be made to work with the mirror system.. but I did not know how. #2. It does not install gnome or kde icons. (If someone wants to submit a new ebuild with this feature.. feel free.) #3. Its slow.. but this is due to the fact it unpacks the rpm's.. then converts them to tar.gz, before finally unpacking and installing. Still much faster then compiling though (i'd say it takes about 10 minutes max on a mediocre box). Remember this is just a development ebuild... I do not intend to see it in portage, and I don't wanna hear complaints about it lacking something, if you wanna add it.. add it. I made this thing because I believe its a waste of time to emerge rpm just to install openoffice. Those interested may wanna look at the source ebuilds... which as of this writing are m61.. but expect over 8 hours of compiling (i don't believe its worth it either unless you really wanna debug it). Sorry for the lengthy report.. but I'm sure you'll like the ebuild. I took bits from portage, some from an old ebuild on bugzilla, and the rest I did. Its minimal.. but it'll do.
Created attachment 48262 [details] openoffice-bin-1.9.69.ebuild
Created attachment 49288 [details] openoffice-bin-1.9.71.ebuild Update
Created attachment 49304 [details] openoffice-bin-1.9.71.ebuild Did a few corrections to the ebuild so that it actually works ;) Still no fancy gnome/kde stuff though, will look at it again later
genstef... thought you should know Running post installation scripts ERROR: Cannot determine spool directory I see that with the ebuild. Dunno if it affects anything yet
I don't have that problem, it installs fine.
It's a non harmful error. Sill: Please consider that this ebuild is quite unfinished and in no way supported ;)
suka: any chance that this will hit portage soon? is there a openoffice-config so that I can have this as default-openoffice?
My current plan is to wait for the beta to arrive which is scheduled Mid-February atm as far as I know, but that all depends how much time I have left from the other stuff. 1.1.x is still top priority. About "default-openoffice", I don't quite understand the question, what should a openoffice-config achieve?
From experience at the release of openoffice 1.1 it is really without merrit to try to build early versions. Even the beta versions tend to have all kinds of problems even getting the stuff to compile. As doing anything with openoffice takes a lot of time, our focus should be on stable releases.
> From experience at the release of openoffice 1.1 it is really without merrit The merit is that people can try out thee beta-version .. come on .. gentoo people are geeks, they will try it out, with the in-portage or with their own ebuild. > to try to build early versions. > Even the beta versions tend to have all kinds of problems even getting the stuff > to compile. Does not count for the binary version, my fan is loud enough that I cannot compile oo, s I just need a binary. > As doing anything with openoffice takes a lot of time, for binary-pkgs not really .. > our focus should be on stable releases. that is sure, but some people nevertheless use the beta ebuilds, so why not just have them in the tree?
@genstef: There are no beta version, this is still alpha ;)
Created attachment 49871 [details] openoffice-bin-1.9.74.ebuild New ebuild for the new snapshot, closer orineted at the latest openoffice-bin ebuild in portage.
Created attachment 49873 [details] openoffice-bin/files/1.9/ooffice-wrapper-1.9 wrapper script for the new openoffice release
awesome ... exactly what i am looking for ....
i just installed 1.9.74, every went ok, except for one problem..... somekool@kommuter ~ $ ls -l /usr/bin/oowriter lrwxrwxrwx 1 root root 7 Feb 2 00:12 /usr/bin/oowriter -> ooffice somekool@kommuter ~ $ ls -l /usr/bin/ooffice ls: /usr/bin/ooffice: No such file or directory somekool@kommuter ~ $ office bash: office: command not found somekool@kommuter ~ $ ooffice bash: ooffice: command not found somekool@kommuter ~ $ type ooffice bash: type: ooffice: not found somekool@kommuter ~ $
openoffice-bin/files/1.9/ooffice-wrapper-1.9 if you place that file there, it is more likely that you will find a /usr/bin/ooffice good luck :)
duplicate of bug #76232 ? anyway, this bug is cleaner and seems to work better
if you're using gtk-2.6* (with gnome-vfs backend...that means most of the gnome-users), then openoffice will crash when you try to open/save a file (when you invoke a gtk dialog) with stuff like: libgnomevfs-ERROR **: file gnome-vfs-cancellation.c: line 133 (gnome_vfs_cancellation_cancel): assertion failed: (gnome_vfs_is_primary_thread()) aborting... how to fix it: go to the "program" folder inside openoffice... if you use this ebuild, that will be somewhere in /opt/OpenOffice-1.9*/program 1. rm libxml2.so* 2. start openoffice and open the open-file dialog..it will crash again. 3. stop openoffice 4. start openoffice again. now it will work ;) the reason is that openoffice uses his "own" libxml2, and when you delete those files, he is forced to use the system libxml2 libraries.. ofcourse, as always, proceed with caution... it worked for me.. i got the info from: http://lists.debian.org/debian-devel/2005/02/msg00337.html
sorry, please ignore my comments.. i tried it today, and it's crashing again, i don't know why.. so please ignore my previous recommendation about deleting libxml2 stuff... it does not help... if you really need to use this openoffice there are 2 ways, but both decrease the functionality: 1. export SAL_USE_VCLPLUGIN=gen before you start openoffice. this will tell him to use the default "skin" (not the gnome one). now all will work, but openoffice is quite ugly this way ;) 2. the problematic part is gnome-vfs. you can tell gtk, that it's file-chooser should use the "gtk+" backend, and not the "gnome-vfs" one. i think if you do this, you will not be able to open files from exotic places like sft:// or samba:// . open gconf-editor, and navigate to /desktop/gnome/interface/file_chooser_backend. set it to "gtk+" (previously it was on "gnome-vfs"). now it should work. p.s: i hope this time i'm not giving wrong advices ;)
Heh, works nice over on this side, like it alot, goood work joecool dude man!
There's 1.9.m79 version available for download already.
Created attachment 52143 [details] openoffice-bin-1.9.79.ebuild version bump
2.0bc out... Genstef, I recommend you take a look at the ebuild, theres gonna have to be a few changes. Also its now in beta, so consider trying to get it in portage (masked of course).
*** Bug 83734 has been marked as a duplicate of this bug. ***
The ebuild lacks of menu shortcut installation in case of "gnome" or "kde" USE flags, and due to the official beta release SRC_URI should point to "mirror://openoffice/stable/2.0beta/OOo_2.0beta_LinuxIntel_install.tar.gz". Regards.
Is it possible to make the package slotable?
Release 1.9.87 is just out.. :-)
Created attachment 54353 [details] openoffice-bin-1.9.87.ebuild Version bump to 1.9.87 snapshot. This is newer then the beta listed on openoffice.org's site. Still no Gnome or KDE shortcuts, but it works.
I found that the symlinks creation is broken. I fixed it in this way: for app in calc draw impress math writer web setup padmin; do - dosym ooffice /usr/bin/oo${app} + dosym /opt/OpenOffice.org1.9/program/soffice /usr/bin/oo${app} done Cheers
Uhm... what I posted before doesn't worl on my amd64. This one let me start applications fine ;) for app in calc draw impress math writer web setup padmin; do - dosym ooffice /usr/bin/oo${app} + dosym /opt/OpenOffice.org1.9/program/soffice.bin /usr/bin/oo${app} done Cheers
I've put 1.9.87 in portage now. The ebuild is based on the work here, so thank you all. Additionally I made some changes: *) Menu entries work now *) GNOME and java support are optional now *) Lot's of unnecessary stuff does not get installed Also it installs to /opt/OpenOffice.org now, no use to put this in a slot btw: It is in package.mask for the time being
Great work! Looks wonderful! Just a suggestion - can it be modified to create symlinks in /usr/bin for oobase and ooffice?
Why the wrapper scprit is called openoffice.org-1.9 ...? why not ooffice , as it used to be? at least the pkg_postinst info should be pointing that out
Please, people. As said in the ChangeLog: This is an unfinished ebuild of a pre-release, which is in package.mask for a reason. So please don't come her nagging about details, this might or might not be resolved in the future, just don't expect the same level of support as with the stable versions.
I don't think that was the point of these sugestions - at least mine was just a suggestion (I can create my own symlinks... :) ) I know it's in package.mask - I'm just trying to give feedback so that by the time it's out of package.mask, it will be the best ebuild ever! :)
Something strange I'm seeing is that sometimes it starts without the GNOME-look to it and sometimes it starts and looks totally like a GNOME application (even the file dialog). But why is it acting schziophrenic and not acting like a GNOME app all the time?
OpenOffice 1.9.100 have been released. http://download.openoffice.org/680/index.html#download
I don't see why you keep responding to this.. its all handled in portage now by Andreas, so consider this obsolete and start new bugs if you have issues. Closing this one for good.
is there a different bug for newest beta release of openoffice or we should reopen this bug ? i think 1.9.120 is out now
Actually: There is no bug for this, as I'm following the releases quite closely, so no need to file a bug or comment for that. btw: It's 1.9.122 which is out ;)
yeah dude.. i closed this bug like... forever ago. Andreas Proschofsky has been doing much better work then I did, he'll keep up with it. so for anyone else DO NOT FILE COMMENTS IN HERE, THIS IS DEAD!!! DEAD, DEAD, DEAD!!
if this bug is dead and we should not post comment here anymore. where should we look at then, for most recent beta version ?
let me give you a hint... MAKE A NEW BUG!!! Its not too friggin hard.. this was for back in the day when i was hackin the ebuild.. now its in portage... so its off my hands.. BTW, new one is in portage.. you got any problems.. file elsewhere.
@Mathieu: New versions go to portage all the time, so what do you want to look for here? And as I said before: I'm following the OOo development quite closely, so no need to "annotate" me of new versions, so no need for bugs about new versions. So, contrary to what joecool has been suggesting: Please don't file bugs just to tell me, that a new version is out.
