|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Update X11 desktop integration | ||
|---|---|---|---|
| Product: | Installation | Reporter: | nospam4obr |
| Component: | code | Assignee: | AOO issues mailing list <issues> |
| Status: | CONFIRMED --- | QA Contact: | |
| Severity: | Trivial | ||
| Priority: | P2 | CC: | caolanm, issues, lohmaier, nesshof, pmladek, rene |
| Version: | DEV300m14 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Unix, all | ||
| Issue Type: | TASK | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
nospam4obr
2008-05-30 12:43:21 UTC
How do other packagers patch the Exec line of the .desktop files ? FWIW one of things that I do is rename all the versioned icons to an unversioned one, and so on for the product name and such references. We're not interested in having different versions of the same product side by side and presenting that version info in the menus etc. We do support (for 3.0) installing broffice.org and openoffice.org together and I just change the launcher from openoffice.org to broffice.org in the broffice.org desktop files and make a copy of openoffice.org called broffice.org with the name location of soffice changed appropriately Thanks for the info. Do you make use of the UNIXWRAPPERNAME variable introduced with issue 75366 and/or the create_tree script ? yeah, both. Though the wrapper name just with "openoffice.org" and a copy and sed on the results afterwards to make the broffice versions. ooo-build-based builds currently use own desktop files, see http://svn.gnome.org/svn/ooo-build/trunk/desktop/. It is just from historical reasons. No volunteer has been found to merge them with the desktop files in sysui yet. Though, we still install the desktop files from sysui into <ooo-home>/share/xdg. And <ooo-home>/share/xdg/qstart.desktop is used by the GNOME quickstart module to start ooffice the right way. This was the reason to introduce the UNIXWRAPPERNAME variable in the issue 75366 and it is still valid. Regarding your proposed change. I think that it makes sense. I think that the freedesktop-menus package really should be sufficient for most current distributions. Moving the package creation to instset_native is step forward, definitely. If you will create the desktop integration in instset_native together with other packages, it will be even much easier for us to start using them and get rid of the ugly duplicit desktop files in ooo-build. I am only not sure about splitting the mime type registration. What do you exactly mean with it? IMHO, if two similar applications appear in the desktop menu, it is perfectly fine to associate them all with the related MIME types. Thanks for the feedback. I think mime type registration and association are two steps: the former bundles a name, extension, magic and icon under a type name, the latter tells the system which applications are able to cope with which file types. In vanilla OO.o, we have a number of potential conflicts inside the registration part: * the names of the pre ODF document types are brand specific * most of the document icons are brand specific and * the symbolic gnome-mime- links to the brand-prefixed icons conflict with those of a different brand package Also there can only be one /usr/bin/soffice ;-) (needed for SDK bootstraping). The idea is to put those conflicting files in a dedicated package, which can be omitted without harming the rest of the desktop integration. I see it now. The split makes sense to me. Unfortunately it looks like I won't get this ready until code freeze :-(, so shifting target. Please take over. Reset assigne to the default "issues@openoffice.apache.org". |