Next: Update Processing, Previous: Importing Applications, Up: Top [Contents][Index]
Information used by update.py to compile the public index comes from two sources:
The original metadata files are simple, easy to edit text files, always named as the application’s package ID with ’.txt’ appended. Additionally, you can use JSON, XML, or YAML for app metadata, using the same fields as the original ’.txt’ format.
Note that although the metadata files are designed to be easily read and writable by humans, they are also processed and written by various scripts. The original ’.txt’ format can be automatically cleaned up when necessary. The structure and comments will be preserved correctly, although the order of fields will be standardised. (In the event that the original file was in a different order, comments are considered as being attached to the field following them). In fact, you can standardise all the ’.txt’ metadata in a single command, without changing the functional content, by running:
fdroid rewritemeta
Or just run it on a specific app:
fdroid rewritemeta org.adaway
The following sections describe the fields recognised within the file.
• Categories: | ||
• Author Name: | ||
• Author Email: | ||
• License: | ||
• Auto Name: | ||
• Name: | ||
• Provides: | ||
• Web Site: | ||
• Source Code: | ||
• Issue Tracker: | ||
• Changelog: | ||
• Donate: | ||
• FlattrID: | ||
• Bitcoin: | ||
• Litecoin: | ||
• Summary: | ||
• Description: | ||
• Maintainer Notes: | ||
• Repo Type: | ||
• Repo: | ||
• Binaries: | ||
• Build: | ||
• AntiFeatures: | ||
• Disabled: | ||
• Requires Root: | ||
• Archive Policy: | ||
• Update Check Mode: | ||
• Update Check Ignore: | ||
• Vercode Operation: | ||
• Update Check Name: | ||
• Update Check Data: | ||
• Auto Update Mode: | ||
• Current Version: | ||
• Current Version Code: | ||
• No Source Since: |
Next: Update Processing, Previous: Importing Applications, Up: Top [Contents][Index]