On 13/10/2018 14:34, Robin Broda via aur-general wrote:
On 10/13/18 2:06 PM, Tom Hale wrote:
The advantages I see of packaging an AppImage are:
* Automatic updates
Automatic in what sense
* GUI integration (eg appname.desktop file and icon) * Easy access to man pages, help docs and changelog * Easy access to files (eg skeleton config files) specified in the help docs
Why would that require AppImage in the loop?
Literally none of your points have anything to do with AppImages.
I believe Tom is pointing to the advantages of deploying an AppImage via a PKGBUILD, rather than of the AppImage format itself. Essentially, using an AppImage as a package `source` like an RPM/deb or other non-native packaging archive. I've seen some projects [citation needed] provide only an AppImage and building from source is non-trivial, so being able to "package" the AppImage could make it easier to use within Arch.