Difference between revisions of "Creating update information for extensions"
m |
m |
||
| Line 10: | Line 10: | ||
#EXTUPDATEINFO_URLS | #EXTUPDATEINFO_URLS | ||
| − | Please note that the program is not intended for validating the xml and schema of the description.xml although it may complain if there is wrong XML. | + | Please note that the program is not intended for validating the xml and schema of the description.xml although it may complain if there is wrong XML. The description.xml must contain a version and a identifier element. |
==Using the Macros== | ==Using the Macros== | ||
Revision as of 12:33, 20 March 2007
| OOo Extensions project
Please view the wiki usage guidelines
|
|---|
|
Categories: Pages: |
| Extensions on the main site |
|
Extensions in other languages: |
For publishing information about an available update one needs to provide the "update information". For more specific information please read the specification "Online Update for Extensions" and the Developer's Guide.
Some XML elements from the description.xml are also part of the update information (version, identifier, dependencies). To avoid maintaining a update information file, we provide a perl program that creates the file based on the description.xml. The program is contained in solenv/bin/make_ext_update_info.pl. The program can be used from a makefile. To facilitate this on can use these macros in a makefile:
- EXTUPDATEINFO_NAME
- EXTUPDATEINFO_SOURCE
- EXTUPDATEINFO_URLS
Please note that the program is not intended for validating the xml and schema of the description.xml although it may complain if there is wrong XML. The description.xml must contain a version and a identifier element.
Using the Macros
EXTUPDATEINFO_NAME=org.openoffice.extensions.testarea.desktop.updateinfo.update.xml EXTUPDATEINFO_SOURCE=description.xml EXTUPDATEINFO_URLS = http://extensions.openoffice.org/testarea/desktop/updateinfocreation/update/updateinfo.oxt .INCLUDE : target.mk
The name provided to EXTUPDATEINFO_NAME will be the name of the update information file. It will be created in the misc directory. The name should be close to the extension identifier, which is contained in the description.xml. Because the identifier can contain arbitrary tokens, not all identifier can be used as file names (for example an identifier containing a '/').
EXTUPDATEINFO_SOURCE is assigned to the description.xml. In the example the description.xml is in the same directory as the makefile. Would it be in a subdirectory then one would provide the relativ path.
EXTUPDATEINFO_URLS receives a list of URLs separated by spaces which are used to create the <update-download> section of the update information file. Each url points to the new version of the extension.
