joplin
joplin copied to clipboard
laurent22
flatpak version
Operating system
- Linux
Application
- Desktop
For linux, can you create a flatpak version?
it would take an extra step but this could work https://github.com/endlessm/electron-installer-flatpak
Flatpak will be a great option for any Linux user to easily install Joplin.
IMHO Flatpak support is a much-needed feature and has several benefits: -The Appimage option always had the problem of integration; Icons in gnome dock never worked and could not be pinned as favorite (at least this was the case with many Appimage Apps including Joplin before i moved to Arch and began to use the AUR package) -Flatpak seems to be more focused on user apps compared to the more server orientated Snap -Is supported by GNOME and most big Linux distros as the de facto future app distribution system -Will be AFAIk used for the renewed push to bring Linux to phones (Librem, Pinephone) -Bring the security advantages of sandboxing -Add the wide and distro agnostic reach of the Flathub App Store if that is wanted Just my 2 cents from a non dev FOSS fan..
Can you please add the support on flatpak, I am a arch linux user and it takes ages to install joplin into my computer from AUR, Linux Mint had previous version, It will be very nice to have joplin on flatpak.
@teynav - I use Manjaro and the below command works for me as another solution. This will install the .appimage. So it should work just fine on Arch too.
wget -O - https://raw.githubusercontent.com/laurent22/joplin/master/Joplin_install_and_update.sh | bash
Regarding the Flatpak support - This is dependent on electron-builder which is already shared above in the ticket.
~ Another user
How about a snap package for Joplin I think they have a good support for electron based desktop apps https://snapcraft.io/docs/electron-apps AppImage is really painful, even with the provided shell script its always better to have an automated solution for updates
And how about an apt repository for debian users?
I would recommend against Snaps. Their backend and main repository is proprietary.
While I wait for my current PR to get reviewed again, I'm messing around with trying to build a flatpak version to solve this issue. So far, what I've found is the flatpak format is barely supported for Electron and is infuriating to setup with only a small handful of node packages available.
This one seems to be the most up to date and stable one available but using it following the page's instructions throws this error in my terminal:
electron-installer-flatpak --src dist/app-linux-x64/ --dest dist/installers/ --arch x64 Creating package (this may take a while) (node:4922) UnhandledPromiseRejectionWarning: Error: flatpak-builder failed with status code 1 at ChildProcess.
(/usr/lib/node_modules/@malept/electron-installer-flatpak/node_modules/@malept/flatpak-bundler/index.js:68:16) at ChildProcess.emit (events.js:321:20) at maybeClose (internal/child_process.js:1026:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) (node:4922) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:4922) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Anyone else attempt this yet or have some insight into this?
I’d love to see more versions released to help make using Joplin on Linux better but AppImage just works for enough users that I wouldn’t put much credence into this topic ever getting really resolved.
I was recently made a member of the official Joplin team, so I’m trying to get a native implementation going to solve this issue all the way, but it’ll probably be a side project without being a part of the actual project.
I actually just sucesfully made a flatpak (ironically using the latest released AppImage)..
I'll possibly drop this onto a github repo if anyone's interested, also I'm happy to submit+maintain an official one on flatpak.org (this would be my first one so its probably not fully standards compliant yet)
EDIT: I've put this into github - https://github.com/starkers/joplin-flatpak
@laurent22 I've just read the guidelines on getting a flatpak packaged up for everyone on flathub. I do need to do some small modifications but otherwise I should be able to get this published pretty quickly but I would like your permission.
So two paths forward really:
- would you like that we can release and update flatpaks with your current process? in which case I'll explore your CI sollution and try to PR that, I'm not fully up to spec on the procedures but I am happy to learn and assist
- I'm happy maintain the official flatpak and build it from the latest AppImage releases. I will of course try to ensure you have ownership of the repo in such a case. (I'll read more and update here if you like)
@starkers, feel free to go ahead with it, you have my permission. As for the way to release it, how would that work if it's part of CI? Does it mean there will be a flatpaks being built and added to the GitHub release files? or the CI will trigger a build somewhere else and file will appear on Flathub?
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
I am still interested in a version of Joplin installable via Flatpak. I believe we are just waiting on work upstream in Electron.
Sincerely, Hutson Keith Betts https://hyper-expanse.net/hutson Encryption Key ID: 0x613EF24A9954F2FE
On Sat, Jun 27, 2020, at 10:33 AM, stale[bot] wrote:
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/laurent22/joplin/issues/738#issuecomment-650575753, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTD7ZS3QZG6WCL7RMOO4Z3RYYGOFANCNFSM4FRTX2HA.
Here's my own Flatpak manifest for Joplin, making use of the AppImage release.
As Joplin is open source I'm not sure if this would be approved for publishing via Flathub as it doesn't build from source, but it's an improvement over the other suggestion here as my manifest uses the extra-data step to download the AppImage release on installation time.
I'm not bothering with building Joplin from source as it's a bit of a problem with Flatpak. It generates an unusable sqlite3_node module, even when forcing the module to be rebuilt. And Flathub's guidelines require offline building without network and with local sources cache, but flatpak-builder-tools/node failing to process Joplin's dependencies recursively.
If anyone wishes to push this forward and publish via Flathub then you're most welcome to use my manifest.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
@tinywrkb It would be approved, as long as you have @laurent22 blessing and setup external-data-checker for updates.
@barthalion Thanks for the feedback. I'm not using Joplin at all, so it would be preferred if someone else that knows the app and can notice when something is broken would maintain it.
For me, Flatpak packaging was kind of novelty and for being able to test it in a sandbox environment.
Nonetheless, I updated the manifest and that should be a bit more in line with Flathub submission, and this fixes an issue with the StatusNotifierItem system tray and the settings folder.
@laurent22 The external editor function will not work as intended with the Flatpak app, that's unless you'll be able to make use of the Portal API, so this should be taken into before Flathub publishing. Would it be acceptable to ship Joplin with this feature broken? adding an influx of users opening bug reports and complaining about it?
Yes! A flapak of Joplin would be great. As a noob linux user I'm badly in need of a good note app. AppImage don't work well with my distro. @starkers please go ahead if you can. Kudos!
If Snap is an alternative for some (the Snap issue is closed now):
@MrCarroll crafted a wonderful package for Joplin (you can find the repo on GitHub):
$ snap install joplin-james-carroll
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.
It would be great if this could be reopened - I think a flatpak would still be welcome.
Thanks.
It's still relevant to me, as I would appreciate managing Joplin via my desktop's existing built-in package manager, as opposed to my current practice of downloading AppImage builds when prompted by Joplin. However, that is my experience on the matter.