Mynacol b3ac1d176c
[FDroidRepoBridge] Simplify json retrieval (#4063)
* [FDroidRepoBridge] Simplify json retrieval

I looked into avoiding the writing-to-file and then reading-from-file altogether. Using a special file path that leaves the data in memory probably wouldn't work. But I'm unsure why we use the `index-v1.jar` file altogether.
The main F-Droid repo [lists](https://f-droid.org/en/docs/All_our_APIs/#the-repo-index) not only `index-v1.jar` (which only makes sense if we were to use the contained signature, which we don't), but also `index-v1.json` and `index-v2.json`. These json files can be fetched with `getContents`, optionally cached, and directly fed into `Json::decode` without using a temporary file. The HTTP transfer encoding can compress the file to a similar degree the jar (=zip) can. That's exactly what this commit uses.

Now the question is whether all the F-Droid repositories out there have this file. I went through the whole [list of known repositories](https://forum.f-droid.org/t/known-repositories/721) and only one repo misses the `index-v1.json` file: [Bromite](https://fdroid.bromite.org/fdroid/repo/index-v1.json). Under these circumstances we can depend on the availability of the `index-v1.json` file.

Closes #4062

* [FDroidRepoBridge] Cleanup not requiring Zip

With the last commit 1152386678151aeafd984061d34248023378bf64, the zip
extension is not required anymore. Don't fail if it's not available.
2024-04-05 17:39:38 +02:00
..
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2023-09-24 18:15:14 +02:00
2023-09-22 20:59:45 +02:00
2022-07-01 15:10:30 +02:00
2024-03-31 21:37:51 +02:00
2022-07-01 15:10:30 +02:00
2023-10-13 00:26:11 +02:00
2023-10-01 19:23:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2024-03-31 22:10:59 +02:00
2024-01-24 19:12:38 +01:00
2023-09-21 22:05:55 +02:00
2023-07-29 00:14:30 +02:00
2024-04-04 19:12:04 +02:00
2023-10-09 08:46:24 +02:00
2023-09-23 19:29:04 +02:00
2022-07-01 15:10:30 +02:00
2022-09-09 20:18:50 +02:00
2024-04-04 19:12:04 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2023-06-07 22:36:21 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-08-10 23:46:17 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2024-02-06 19:32:05 +01:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2024-03-31 03:38:42 +02:00
2022-07-01 15:10:30 +02:00
2023-09-22 09:38:05 +02:00
2024-04-04 19:12:04 +02:00
2023-09-24 00:03:21 +02:00
2024-01-25 13:03:00 +01:00
2023-06-07 22:36:51 +02:00
2024-03-31 21:32:27 +02:00
2023-12-30 01:33:31 +01:00
2023-09-22 20:59:45 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2023-09-21 22:05:55 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2023-11-21 17:00:02 +01:00
2024-03-31 21:32:27 +02:00
2023-09-21 22:05:55 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-12-13 21:04:57 +01:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00
2022-07-01 15:10:30 +02:00