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 metadata files are simple, easy to edit text files, always named as the application’s package ID with ’.txt’ appended.
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. They are capable of rewriting the entire file when necessary. Even so, 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 metadata in a single command, without changing the functional content, by running:
fdroid rewritemetadata
The following sections describe the fields recognised within the file.
• Categories: | ||
• License: | ||
• Name: | ||
• Auto Name: | ||
• Web Site: | ||
• Source Code: | ||
• Issue Tracker: | ||
• Donate: | ||
• FlattrID: | ||
• Bitcoin: | ||
• Litecoin: | ||
• Summary: | ||
• Description: | ||
• Maintainer Notes: | ||
• Repo Type: | ||
• Repo: | ||
• Build Version: | ||
• AntiFeatures: | ||
• Disabled: | ||
• Requires Root: | ||
• Archive Policy: | ||
• Update Check Mode: | ||
• Vercode Operation: | ||
• Update Check Data: | ||
• Auto Update Mode: | ||
• Current Version: | ||
• Current Version Code: | ||
• No Source Since: |
Next: Update Processing, Previous: Importing Applications, Up: Top [Contents][Index]