| Summary: | AppImage backend | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | roudou <docevrard> |
| Component: | discover | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | CC: | aleixpol, nate, null, silopolis, telefonciek |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
roudou
2022-02-06 16:03:18 UTC
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. |