-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a Flatpak as software package for Linux #105
Comments
Would really appreciate if someone would make this happen! I'm having issues with running on my Arch install; both the package in the AUR, attempting to install the .deb with debtap, and running the Windows version in Wine fail for me. |
@KNO56 There is also a CLI app, I know we have some users on Arch using that - https://github.com/trustcrypto/python-onlykey |
@KNO56 the package in AUR stopped working at some point due to fontconfig updates. I've pushed an update to 5.2.0 which should work fine now. Creating the AUR package is tedious, though. It actually downloads the .deb file built obviously for debian-based distributions, unpacks it and packs it back for Arch. That seems strange at first, why bother getting the .deb package and then unpack it, instead of just calling The reason is that the release command for linux actually only works under Debian (or Ubuntu or any other derivative) and uses the assumption that this is going to be used on such distribution by directly calling dpkg-deb. Creating release task just for arch is would need pretty much copy-pasting release_linux.js and change it slightly. Probably introducing flags for the release command for arch would work, too. However, that means we've just covered two major distributions. What about the rest? This made me to request a Flatpak package which would benefit users of all distributions. On a second thought AppImage would work, too. |
@vladimiroff We did publish a snapcraft package, I would like to do a Flatpak as well but just finding the time to do this. Any assistance here would be great, here is the snapcraft.yaml, it simply extracts the .deb and links to the command and the desktop file.
Documentation has been updated to include snap instructions - https://docs.crp.to/linux.html |
Many thanks @vladimiroff, it works like a charm now! |
"Our experience shows that Flatpak has been a more stable platform than Snap, which has had many deployment bugs over the years, so we decided to deprecate it in favour of Flatpak." |
I'm not familiar with how to deploy a flatpak. Anyone from the community with experience with this that wants to try this? Not sure if you could convert DEB to flatpak from releases here https://github.com/trustcrypto/OnlyKey-App/releases/tag/v5.3.6 |
They are usually published on You can definitely start with a I can start it and take it to completion, at least from the |
@x80486 Great, thank you! If you can share the script or method you use to generate the Flatpak I can take it from there. |
Hi, I took a shot at this and have produced a working flatpak of the latest version (5.5.0). Build instructions and other details are all in my repo: https://github.com/Ian2020/io.onlykey.OnlyKey-App I'm looking for feedback, it seems to work for me but please raise any issues in my repo though rather then here. It would be great if onlykey could take on the maintenance of this so we can ultimately have an official version available on flathub. I don't think people would trust a build from me or a third-party of such a security app. There were quite a few hurdles to making this. The main one is that the nw dependency had a broken installer which I had to fix by pointing the build at my own fork of their code. They have now fixed the issue but it's not yet released. So I think an official build might want to wait for the next release of NWJS at least. |
Flatpak is a technology for building, distributing, installing and running applications – primarily targeted at the Linux desktop and desktop applications.
Doing this will enable usage on other than debian or debian-based distributions.
The text was updated successfully, but these errors were encountered: