Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by simosx on Friday June 14, 2019 @05:32AM
(#20181606)
For snap packages, you can use the build servers at https://snapcraft.io/build
Point to your github repository with the snapcraft.yaml file and it will create the snap package for you.
I think the publishing is very straightforward, and you can get a new package published very quickly.
Of course, you need to work a bit in creating the snapcraft.yaml configuration file in the first place.
Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by app4soft on Friday June 14, 2019 @05:46AM
(#20181670)
For AppImage packages, follow AppImageKit instructions.[0]
You can use Travis CI servers (.travis.yml file in your repo on GitHub) with linking linuxdeployqt tool.[1]
For deployment built files back to GitHub as assets also use uploadtool Shell-script.[2]
[0] https://github.com/appimage/AppImageKit
Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by loginwithgithub on Friday June 14, 2019 @10:34AM
(#20183324)
Why do you find them annoying? I love them. Every application is just one file that I can freely move and copy around, can't be any simpler than that.
Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by yjftsjthsd-h on Friday June 14, 2019 @03:29PM
(#20185965)
Take a dozen such applications, then have a security vulnerability show up in a core library. Still simple?
Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by AnIdiotOnTheNet on Friday June 14, 2019 @08:40PM
(#20187784)
Yes, it just isn't "secure" as far as the security-for-the-security-gods types are concerned.
Re:Comparing LibreOffice Versions: AppImage, Flatpak, and Snap
by loginwithgithub on Saturday June 15, 2019 @02:44AM
(#20188711)
It depends on how often the stuff in the packages gets updated, not on the package format.
Flatpak has been quite nice when I've used it, if a bit more awkward to figure out first time.
Snap is fine, but the actual publishing side of it I found quite confusing and arduous when I tried it, so from a developer point-of-view I would probably avoid it (unless it improved a lot in the last year).