It's very refreshing to see a chromium browser going open source, one especially that has extensions support. Would it be possible to submit the package to the F-Droid repo? It would help people who are not so keen on downloading apps from google.
In theory it's possible but before I think F-Droid should try to onboard Chromium (I think it's not the case) as Kiwi depends on Chromium
An alternative would be to create a F-Droid repo, if this is enough it's a possibility too
An another alternative, would be to be inclued into an already managed F-Droid repo, like the @IzzySoft one : https://apt.izzysoft.de/fdroid/index/info
One downside would be that your F-Droid releases will depend on Izzy support obviously.
Outside of that, here´s how to create a F-Droid repo easily with the repomaker. https://www.f-droid.org/en/tutorials/create-repo
I'm afraid it won't fit into my repo because of the size limit. Reading "based upon Chromium", the APK will certainly be larger than 30M (the limit in mine).
But there's an F-Droid repo focused on web browsers here, maintained via this GitLab repo. And it already mentions Kiwix, so it should fit: "Unofficial F-Droid repository for various apps, including Firefox, Kiwix and Signal"
I'm afraid it won't fit into my repo because of the size limit. Reading "based upon Chromium", the APK will certainly be larger than 30M (the limit in mine).
But there's an F-Droid repo focused on web browsers here, maintained via this GitLab repo. And it already mentions Kiwix, so it should fit: "Unofficial F-Droid repository for various apps, including Firefox, Kiwix and Signal"
Thanks for the prompt reply, completely forgot that ¨unoficial mozilla repo¨ has changed. So yeah, in that case, maybe propose to serve built and officially signed applications to this repo.
I don’t think asking for this repo owner to make automated builds of the Kiwi Browser repo would work, as they are only redistributing official built APKs in an automated way.
And it already mentions Kiwix, so it should fit: "Unofficial F-Droid repository for various apps, including Firefox, Kiwix and Signal"
You’ve mistaken Kiwi Browser with Kiwix which is a Wikipedia reader ! :laughing:
Anyway, I´ve submitted an issue here on their repo : https://gitlab.com/rfc2822/fdroid-firefox/-/issues/8
You’ve mistaken Kiwi Browser with Kiwix which is a Wikipedia reader !
No, I haven't (but I've waited for that comment :rofl:). If I had mistaken it, I had written "it's already there so what are you asking". I know what Kiwix is – and I've checked with your Readme in advance to see whether it relates. All I wanted to say is that repo is not restricted to Firefox and derivates (with which it originally started). And I wanted to have a laugh – so, mission accomplished :laughing:
All the best then! And thanks for considering my repo! :green_heart:
I'll work on an automated build in the coming days (I need to read and understand how the GitHub CD pipeline works). Normally it shouldn't be difficult if you are interested into building yourself, it's just superslow.
@kiwibrowser
Please use automated building to also add APKs to release section
Maybe, https://github.com/marketplace/actions/automatic-releases
Doing it for automatic build :)
Will this happen soon?
Keen to give this a go now Firefox has broken extensions on Android, as I'm sure many are.
@Dev-i-l while that certainly is good, it's not the same (close, but no cigar). People trust F-Droid. People are constantly getting discouraged from installing apps they find "on some website". Plus, side-loading means you've got to care for updates manually.
I'd say it's still preferable having it available in "F-Droid proper". Your choice, of course.
@IzzySoft
As you can see in the Actions tab, the reproducible builds are working very well since that topic was started, but I need to create a separate repo for F-Droid; because on F-Droid you cannot distribute Chromium-based browsers in the main repository (and there are tons of good reasons to it).
I haven't checked the doc how to create a F-Droid repo, but it makes sense to do it, so let's keep in touch; it'll can be convenient to users.
Yes, definitely! Once it's there, I should put it into my list of available F-Droid repos.
In the forum, we recently had someone asking for help on setting up a repo; they managed themselves, but picked up some hints missing from the docs (like making sure the URL ends in /fdroid/repo, which the docs state without giving reason – it's so the intent filter picks it up and, if a user taps such an URL, the F-Droid client jumps in offering to add the repo). So basically, those docs should be quite straight to follow.
any update on this ?
@kiwibrowser Any update on this?
Most helpful comment
I'll work on an automated build in the coming days (I need to read and understand how the GitHub CD pipeline works). Normally it shouldn't be difficult if you are interested into building yourself, it's just superslow.