4 ms·

I find AppImage files quite annoying, I must admit. I understand that it's annoying packaging for all the different Linux distros, but this doesn't feel like th

I find AppImage files quite annoying, I must admit. I understand that it's annoying packaging for all the different Linux distros, but this doesn't feel like the solution. Maybe renaming them and dumping them in /usr/local/bin would make them integrate better with the OS, but I usually just avoid them. 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).

simosx 7y ago
For snap packages, you can use the build servers at https://snapcraft.io/build 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.
app4soft 7y ago
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 https://github.com/appimage/AppImageKit [1] https://github.com/probonopd/linuxdeployqt https://github.com/probonopd/linuxdeployqt [2] https://github.com/probonopd/uploadtool https://github.com/probonopd/uploadtool
loginwithgithub 7y ago
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.
- yjftsjthsd-h 7y ago
  Take a dozen such applications, then have a security vulnerability show up in a core library. Still simple?
  - AnIdiotOnTheNet 7y ago
    Yes, it just isn't "secure" as far as the security-for-the-security-gods types are concerned.
    - loginwithgithub 7y ago
      It depends on how often the stuff in the packages gets updated, not on the package format.

simosx 7y ago

For snap packages, you can use the build servers at https://snapcraft.io/build 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.

app4soft 7y ago

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 https://github.com/appimage/AppImageKit [1] https://github.com/probonopd/linuxdeployqt https://github.com/probonopd/linuxdeployqt [2] https://github.com/probonopd/uploadtool https://github.com/probonopd/uploadtool

loginwithgithub 7y ago

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.

yjftsjthsd-h 7y ago
Take a dozen such applications, then have a security vulnerability show up in a core library. Still simple?
- AnIdiotOnTheNet 7y ago
  Yes, it just isn't "secure" as far as the security-for-the-security-gods types are concerned.
  - loginwithgithub 7y ago
    It depends on how often the stuff in the packages gets updated, not on the package format.