The oooqs v2.02 don't work with ximian-openoffice. It start together with KDE, but it do nothing. When I select from quickstarter popup menu any component of openoffice, it do nothing.
I added my email address to CC, because I'm having more or less the same problem. This is the combination I'm using: > equery list openoffice Searching for package 'openoffice' in all categories among: * installed packages [I--] [ ] app-office/openoffice-1.1.1-r1 (0) > equery list oooqs Searching for package 'oooqs' in all categories among: * installed packages [I--] [ ] app-office/oooqs-2.0.2 (0)
Same here, also tried with oooqs-2.03
Yep, that results from xoo using another install dir that vanilla OOo, but there is no easy solution for that...
As I wrote in comment #1 I have the same problem with OpenOffice.org. I'm not using Ximian OOo, so the reason Ximian OOo using different paths is not an explanation why I'm experiencing the problem. Thanks for your help. This is what I'm using: > equery list openoffice Searching for package 'openoffice' in all categories among: * installed packages [I--] [ ] app-office/openoffice-1.1.1-r1 (0) > equery list oooqs Searching for package 'oooqs' in all categories among: * installed packages [I--] [ ] app-office/oooqs-2.0.2 (0)
Karim: Next time maybe open a new bug. It is rather confusing trying to solve two problems on one podium.
I found reason of the error. At first start oooqs looks into the file ~/.sversionrc to find what versions of openoffice are installed in the system. In my system there is file ~/.xversionrc. I created symbolic link from .xversionrc to sversionrc and now it is running. I know that it is temporary workaround, but reason is found.
I filed bug #61608 as Paul de Vrieze recommended me (sorry for the space problem on the podium ;-). I added some strace info which led me to get a workaround for the problem.
Just commited 2.0.3-r1 which now also works with openoffice-ximian, please be sure to read the einfo at the end of the build. Anyway, we'll have to find a cleaner solution in the future, this one involves patching oooqs which is not optimal for various reasons