SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports ***bonjour pourquoi ne pas proposer des Appimages qui n(interfèrent pas root comme flatpak ou snap merci STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
why not offer Appimages that do not interfere with root like flatpak or snap
Adding support for AppImageHub (https://www.appimagehub.com/) and integrating features of both AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) and AppImageUpdate (https://github.com/AppImage/AppImageUpdate) would ice the already tasty Discover package management cake :)
I think it is a very good idea. It could be implemented in phases 1. Local file support (Opening AppImages, integrating them with systems, and updating like AppImageLauncher) - it could be easily done with help of libappimage 2. Add AppImage repository (just use official database https://github.com/AppImage/appimage.github.io#how-to-use ) it may require some JSON parsing, but should be also doable
It's a good idea, but requests like this are just too huge to fit within a bug report/feature request, unfortunately. If someone wants an AppImage backend, they're going to have to write it.