[aur-general] PKGBUILD for an .AppImage
Tom Hale
tom at hale.ee
Sat Oct 13 12:06:34 UTC 2018
On 12/10/18 12:06 am, Eli Schwartz via aur-general wrote:
> The fundamental purpose of AppImage is to offer standalone software that
> does not integrate with the package manager, in return for not depending
> on the package manager.
>
> What is the point of packaging one into a pacman package? If people
> wanted appimages they would download them and run them as intended...
> not by extracting the contents and incompletely copying them to /usr
The advantages I see of packaging an AppImage are:
* Automatic updates
* 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
> Programs which build using private libraries belong in /opt either way,
> definitively not in /usr/lib.
Cheers, I'll symlink to there.
--
Tom Hale
More information about the aur-general
mailing list