Feature request: Add RSAF to F-Droid repo

[archandanime]

Currently there is no way to automate RSAF update except for manually downloading the APK file from your repo. Even though it only takes a few taps to to update RSAF, I believe it would be really nice to have RSAF automatically updated on the background.

I really appreciate your app, it is simple but extremely useful(I like your apps a lot since DualBootPatcher in the old days). I couldn't ask more but maybe someone else also wishes to have the app automatically updated.

Thank you!

[chenxiaolong]

I think this is a great idea, but it isn't something I have time for right now, unfortunately.

If someone else were to create the necessary metadata files and submit a PR, I'd accept it. That said, I'm not sure if RSAF can be accepted into the main F-Droid repo. One of the requirements listed at https://f-droid.org/en/docs/Inclusion_Policy/ is:

Binary dependencies such as JAR files have to be built from source or installed from Debian repos.

RSAF is completely open source and so is everything it depends on. However, it does require gomobile, which is a package that needs to be installed on the host machine. (It's outside of the scope of Android's regular gradle build scripts.) gomobile currently isn't packaged in Debian's repos, so as it is right now, I don't think F-Droid's build servers are able to build RSAF.

---

In the meantime, I'd suggest using https://github.com/ImranR98/Obtainium to update directly from Github Releases.

[archandanime]

Thank you for the quick reply! I'd look take a look at Obtainium.

[alexanderadam]

@archandanime you can also use RoundSync in the meantime.

It's available on F-Droid if you activate the IzzyDroid repo.
SAF is can be activated from settings although it is marked as experimental and the documentation got lost.

It doesn't support random seek though.

[iexos]

However, it does require gomobile, which is a package that needs to be installed on the host machine.

It seems there are quite a few apps on f-droid using gomobile, so inclusion should not be a problem: 1 2 3

[iexos]

I gave it a shot, though I don't really know what I'm doing and something regarding go/gomobile does not work:

https://gitlab.com/iexos/fdroiddata/-/blob/com.chiller3.rsaf/metadata/com.chiller3.rsaf.yml
https://gitlab.com/iexos/fdroiddata/-/jobs/7748334932

If anyone wants to pick it up, feel free to do so :)

[iexos]

I also opened a Request for packaging containing further discussion

[aicynide]

I gave it a shot, though I don't really know what I'm doing and something regarding go/gomobile does not work:

https://gitlab.com/iexos/fdroiddata/-/blob/com.chiller3.rsaf/metadata/com.chiller3.rsaf.yml https://gitlab.com/iexos/fdroiddata/-/jobs/7748334932

If anyone wants to pick it up, feel free to do so :)

Add -checklinkname=0 in gomobile command

[iexos]

I spent some more time with it and got it to build!

However, automatic checking for updates will not work since f-droid requires to find the VersionCode statically somewhere, e.g. in the repository or in the release metadata.
@chenxiaolong would it be possible to add the VersionCode somewhere? Doesn't need to be in the repo itself, could also be part of the name, filename, description of the release.

[chenxiaolong]

@chenxiaolong would it be possible to add the VersionCode somewhere? Doesn't need to be in the repo itself, could also be part of the name, filename, description of the release.

It would be pretty easy to change the filename pattern from RSAF-$versionName to RSAF-$versionName-$versionCode (eg. RSAF-3.3-197376-arm64-v8a-release.apk). Would that be sufficient?

[iexos]

It would be pretty easy to change the filename pattern from RSAF-$versionName to RSAF-$versionName-$versionCode (eg. RSAF-3.3-197376-arm64-v8a-release.apk). Would that be sufficient?

Yes, that would be sufficient :)

With that we have the minimum requirement with which I will add the inclusion PR to F-Droid. There is more that would be good to do, but I don't want to put the effort in:

• adding metadata within the repo to have screenshots and translatable description within f-droid
• making the build reproducible

[chenxiaolong]

Done in #136

[iexos]

• adding metadata within the repo to have screenshots and translatable description within f-droid

This is actually required, I will make a PR when I come around to it. Feel free to do it yourself as well.
@chenxiaolong there are different options, do you care which one to choose?

[chenxiaolong]

I am fine with including that metadata in this repo as long as it's minimal and doesn't require extra work when I release new versions.

The main thing that concerns me is the changelogs. I can't tell from the documentation if that is optional. I prefer to keep a single CHANGELOG.md at the root of the repo since that's how I manage the changelogs for all of my projects. I'd rather not to have to copy the contents to some other changelog file for every release, even if that process was automated.

For the title, description, screenshots, etc., I have no problem with those since they almost never change.