You are not logged in.
Hello,
I picked up the existing PureRef package on the AUR, and it came to my attention that PureRef is distributed as an AppImage inside of a deb file. I've never packaged an AppImage before, and I was unclear on some of the search results here, so I wanted to double check:
1. The PureRef AppImage makes use of fuse2 when it is launched with normal user permissions. PureRef is typically launched with normal user permissions, so it seems like fuse2 should be a required dependency. But PureRef can technically be launched as root without fuse2. So, does that actually make fuse2 an optional dependency by technicality?
2. And then, since AppImages are essentially self-contained file systems, I suppose I'll need to move the /usr/bin/PureRef binary to /opt/PureRef instead, is that right?
Thanks for your help!
Last edited by meepzh (2024-12-13 21:56:16)
Offline
The current source is a DEB. Where are you seeing an AppImage?
Either way, GUI applications should never be run as root.
Offline
When running the binary without fuse2 under normal permissions, it errors out with the message, "Cannot mount AppImage, please check your FUSE setup", so I figure that file is an AppImage. Is that message misleading?
But thank you for that link, I suppose that answers that first question then.
Offline
Oh my... Upstream packages an AppImage in a DEB as the "binary"?
Offline
Ah yes, the deb evidently unpacks an AppImage into /usr/bin/PureRef
Offline