My findings are for openoffice-bin, but I guess they apply (at least partly) for its non-binary counterpart, too. First of all desktop-file-validate from dev-util/desktop-file-utils throws a number of errors and warnings, which are easily fixable with the exception of the KDE specific "InitialPreference" one. The KDE guys are unfortunately really sloppy not prefixing their specific extensions even in KDE 4. Another issue issue is that OOo installs its desktop entries in /usr/lib/openoffice/share/xdg as well as in the standard path /usr/share/applications, with the exception of extension.desktop and qstart.desktop - for whatever reason. Furthermore, the binary to be executed by extension.desktop is "unopkg", but OOo installs only /usr/lib/openoffice/program/unopkg.bin. Similar for qstart.desktop. You may use validate_desktop_entries() from eutils.eclass to catch desktop entry errors (not warnings for verbosity reasons) in your ebuilds, btw..
(In reply to comment #0) > First of all desktop-file-validate from dev-util/desktop-file-utils throws a > number of errors and warnings, which are easily fixable with the exception of > the KDE specific "InitialPreference" one. The KDE guys are unfortunately really > sloppy not prefixing their specific extensions even in KDE 4. Been fixed upstream, wait until next vulnerability to get a release... :P http://www.openoffice.org/issues/show_bug.cgi?id=85816
openoffice has different desktop-files, so this should only apply to -bin. As this seems to be fixed, we'll get the fix with the next release (which should be very soon). Closing
All these issue are still present 2.4
(In reply to comment #3) > All these issue are still present 2.4 > Still in this case this should be handled upstream, as that's where we are taking the binaries from...
(In reply to comment #4) > (In reply to comment #3) > > All these issue are still present 2.4 > > > > Still in this case this should be handled upstream, as that's where we are > taking the binaries from... > Took another look at the upstream bug: The child workspace where those fixes went (ause084) was integrated for OOo 3.0, so that's when those cleanups should appear.
