keepass2android
keepass2android copied to clipboard
PhilippC
Availability through f-droid?
Is it possible to make it available via f-droid or is there a reason its not there? As its open source it should be possible.
If not, it should be possible via a custom repository for keepass2android so its available for users without google play store https://f-droid.org/docs/Setup_an_F-Droid_App_Repo/
greets
There has been a packaging request on F-Droid's Gitlab site. Maybe someone can help out @PhilippC with the licensing questions?
I think that's the policy for submitting to f-droid: https://f-droid.org/wiki/page/Inclusion_Policy
It links to the gnu.org list of licenses: https://www.gnu.org/licenses/license-list.html . As far as I understand all GPLCompatibleLicenses and GPLIncompatibleLicenses are fine.
@PhilippC: I think the best option is to disable all proprietary things through a F-Droid build flavor. It should be the de-facto standard, and one example is riot-android.
Just by the way, Syncthing is comfortable.
I have created an fdroid branch which should resolve the licensing issues. For updates, please refer to https://gitlab.com/fdroid/rfp/issues/5
@PhilippC will the fdroid-build have entirely the same features as the master?
if not - or as a quick workaround, since it isn't completely done for now - please release an apk at github/gitlab. i'm sure @IzzySoft will be so kind to pick it up and add to his F-Droid Repository.
If it's a build different from F-Droid, it should preferably have a different package name then to avoid confusion. But yes, feel free to ping me then.
Presumably proprietary file syncing features are removed, and that should be the only difference.
@ishitatsuyuki for sure all proprietary parts won't be included in an fdroid-version, but what specific features will be affected...?
...so the nonet-version may be identical and easier to publish via f-droid?
Hm, if you don't want to hassle much around it would be possible to set up your own repo for f-droid: https://f-droid.org/docs/Setup_an_F-Droid_App_Repo/ You may consider it, you don't have to change anything at the app itself. And everybody gets updates if you update it. But via the f-droid repo would still be wonderful : D
@natrius that's why i asked in https://github.com/PhilippC/keepass2android/issues/38#issuecomment-341652382 to publish an apk-file which can be included into an own repo.
Is there an update? Or is there even the possibility to download the .apk ?
@natrius the apks are still on the releases page and the app is still not on F-Droid.
You could save other people's time, simply by reading and clicking.
@alexanderadam that RFP is still stalled, so the app itself is not on F-Droid yet.
@IzzySoft I know. That's the reason why I wrote that it is still not available and linked to that rfp. :wink:
It's somehow a pity. There are a some really good KeePass clients like keepass2android and keepshare that are open source bot not on F-Droid yet. Currently I'm using KeePassDX because it looks more modern than keepassdroid.
Is there any client I could have missed?
@alexanderadam keepshare hasn't been updated for more than a year now (last commit was in 6/2017, last release in 2016). TinyKeePass is at F-Droid as well.
If you follow the RFP for Keepass2Android you will find that @PhilippC and I are working to get it into my repo at least, but that might take a little (Philipp might be able to give an ETA).
@IzzySoft thank you very much! definitely an improvement. do you think is it somehow possible to get the add-ons into a repo - at least into yours, as long as they are also not in the main one?
@DJCrashdummy hard to say, as most of the linked ones don't have APKs in their repos. And the other 2 (K2AUSBKeyboard and AutoFill Plug-in) are already in my repo :wink:
@IzzySoft i knew about the K2AUSBKeyboard but somehow missed the AutoFill Plug-in... :confused: i'll take this as an ok from your side as soon as we get some APKs. :wink:
@DJCrashdummy you didn't mention the first (but had me check! evil, evil :rofl:) – and couldn't have seen the second as I adopted that only after your previous comment was posted. And you can take that as a "not OK as long as there are no APKs" – though I'll probably take them in when they're there; but wouldn't it be better to file an RFP with the official repo first? If they accept and build it, there'd be no reason for Philipp to provide APKs in his repos.
Any news on pushing this app to F-Droid eventually? I'd rather install it from F-Droid than from Google Play.
@nazar-pc it's currently available in my repo – but I agree it should be in the official one. The reason why it isn't can be found here: it's a Xamarin app, and would need an F-Droid team member with Xamarin experience to build…
Hello, Could you add some kind of tl;dr about current f-droid status to readme, please? I see that issue got duplicated multiple times and people asking for updates, so it will be easier for all to find that information in readme.
BTW, link to @IzzySoft repo in readme is good idea, too
