[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#75809: Hard-coded version code is unsuitable for automated F-Droid A
From: |
Peter Oliver |
Subject: |
bug#75809: Hard-coded version code is unsuitable for automated F-Droid Android package builds |
Date: |
Fri, 24 Jan 2025 17:13:10 +0000 (GMT) |
On Sun, 19 Jan 2025, Peter Oliver wrote:
I notice that F-Droid is able to automatically build packages when a new Git
tag is made. However, in order to do that, it needs to be given an integer
version number (called a version code;
https://developer.android.com/studio/publish/versioning#versioningsettings).
It can look for that either in the name of a Git tag, by searching in a file
within Git, or by fetching some data over HTTP
(https://f-droid.org/en/docs/Build_Metadata_Reference/#UpdateCheckData).
Currently, this is hard-coded to 30 in java/AndroidManifest.xml.in, but
something like 300093000 would be needed (for 30.0.93). Could we set that
for them?
Attached are two patches addressing this.
--
Peter Oliver
0001-Note-that-.apk-packages-for-Android-can-be-installed.patch
Description: Text document
0002-Set-android-versionCode-as-an-integer-derived-from-t.patch
Description: Text document
- bug#75809: Hard-coded version code is unsuitable for automated F-Droid Android package builds,
Peter Oliver <=