Skip to content

Instantly share code, notes, and snippets.

@est31
Last active September 27, 2018 11:41
Show Gist options
  • Save est31/85bf9a22f56bdf1a025e to your computer and use it in GitHub Desktop.
Save est31/85bf9a22f56bdf1a025e to your computer and use it in GitHub Desktop.
A collection of things to do in order to be nice to f-droid packagers

How to release a godot application for f-droid

In the best case, you should:

  1. tag your releases. This way, one always knows which commit to package for a specific release
  2. create and maintain an export.cfg, with an icon, and version numbers raised at each release

Explanations why these things are useful for packagers, and how they are done, and done best, can be found below.

Tagging releases

Either use github releases (for an how-to see here), or tag releases with your git client (github will automatically create a github release).

This is important so that packagers can find out which commit to package for a given release name.

Creating and maintaining export.cfg

Create an export.cfg file, with at least settings for android. Technically, f-droid (and android) requires to have raising version codes with every release. But there are other things you should/could do:

  • create and set an icon (package/icon)
  • customize the unique name (package/unique_name), it should be according to java package naming conventions
  • customize the app's name (package/name)
  • set version name (version/name) and update it every release
  • set version code (version/code) and update it every release

Those version code/version name updates need to be done in some commit between two releases.

How to edit an export.cfg file

Either do it manually in an editor, or, which is much easier, via the options part of the export->android menu in godot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment