On 8/16/22 07:05, Siard wrote:
Why, AppImages can just be made executable and then executed.
For example, I always had a package like Everdo-1.7.8.AppImage in /usr/local and a file named 'everdo' in /usr/local/bin containing this simple script:
#! /bin/sh /usr/local/Everdo-1.7.8.AppImage
so I can start the program with the command 'everdo'.
Okay, I got it. I stay miles away from any flatpack, docker or other containerized nonsense. The size and version duplication is just not my taste. A simply "hello world!" Qt application can take of 100M of dependencies and if you change a minor version you compile against, you can need another 100M of dependencies for "hello world2!". If /usr/local/bin permission are reset -- find out what in sysconfig or apparmor is doing it and get rid of that setting. That would drive me nuts. (yes there is a good argument to restrict ownership of /usr/local/bin for new users -- but, there is no reason you don't have full control over that too) -- David C. Rankin, J.D.,P.E.