Allow "-l" and "-q" to show only available AppImages
As you already know, "AM"/"AppMan" installs and manages not just AppImages, but also portable applications.
This release helps the users of AppImages, the ones that only look for AppImages, thanks to the new suboption "--appimages" to be used in "-q" or "query" and "-l" or "list".
Usage:
am -l --appimages
am -q --appimages ${KEIWORD1} ${KEYWORD2} ${KEYWORD3}
or
appman -l --appimages
appman -q --appimages ${KEIWORD1} ${KEYWORD2} ${KEYWORD3}
simplescreenrecorder-2024-08-08_22.55.41.mkv.mp4
The new lists come from the main ones and only contain unique AppImages, so no helpers for metapackages like "kdeutils" (27) and "kdegames" (40).
"AM" database statistics
We can divide the installation scripts into "unique programs" (AppImage and other portable formats), "helpers" (keywords to facilitate the installation of metapackages, such as unique programs) and "launchers".
Until today, August 09, 20024, this is the situation for the x86_64 architecture:
- 2119 unique programs, and of these...
- 1922 are AppImages
- 197 are standalone programs and command line utilities
- 40 helpers for "kdegames"
- 27 helpers for "kdeutils"
- 2 helpers for "platform-tools" (adb and fastboot)
- 1 helper for "node" (npm)
- 9 launchers (ffwa, FireFox WebApps, or profiles)
Among other changes
Option "-f" or "files", add notes on appimage2 and appimage3 usage
The names "appimage2" and "appimage3" will remain in effect until the "fusermount" issue is resolved upstream. See #818 for more details.
Full Changelog: 7.4...7.5
What next?
Now that AppImages can be listed separately from other apps, helpers and launchers, and have a clearer picture of what we actually have in the database... the next release, 7.6, will start working on verifying AppImages that have verified code and unofficial, closed-source ones, to improve security and help you choose more trusted applications.
Stay tuned!
PS: thanks to @probonopd for this imput
