[aur-general] PKGBUILD for an .AppImage

Eli Schwartz eschwartz at archlinux.org
Thu Oct 11 17:06:39 UTC 2018

On 10/11/18 12:53 PM, tom at hale.ee wrote:
>> Looks like nixnote2 is already on the AUR and properly built from
>> source, both stable and -git.
>> A binary package ripped from an AppImage is probably the last thing
>> you should be proposing...
> I am the packager of the -git package and will likely disown the pinned
> package.
> Could you justify your assertion?
> It seems I will need to go with the whole appimage... Upstream won't
> change the linkage to a versioned library filename.

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

Programs which build using private libraries belong in /opt either way,
definitively not in /usr/lib.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20181011/a533c84a/attachment.asc>

More information about the aur-general mailing list