Hello Joachim, On Tuesday 25 May 2010, 11:03, Joachim Lingner wrote: > > > > this is true if you take the approach of creating one OXT file for each > > platform/architecture, so you must have > > > > a) MyExtension_Linux_x86.oxt > > b) MyExtension_Linux_x86_64.oxt > > c) ... > > > > all with the same extension identifier in description.xml but > > The identifier must be different! Otherwise, using the online update you > could download and install an extension, which is not supported on your > platform. The extension manager uses only the identifier and version to > determine if there is an update available.
ups yes, you're right (it seems I take always the other all-in-one-approach): http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extension_Identifiers "the identifier MUST be unique. This is also the case when two extensions are logically the same but support different platforms. In this case one can achieve this uniqueness by adding a platform string to identifier. " Nice we caught your attention. According to http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Target_Platform "Do not confuse these tokens with those used to specify a native library in the manifest.xml. We will unify the use of the tokens in one of the future releases." I couldn't find any issue about this in the issue tracker. Do you have any idea if this is already planned? (This will be the real solution for the OP) Regards -- Ariel Constenla-Haile La Plata, Argentina
signature.asc
Description: This is a digitally signed message part.
