| Summary: | Better Appimage integration, auto-creation of menu entries | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Henning <boredsquirrel> |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | wishlist | CC: | aleixpol, nate |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.26.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Discover's primary purpose in life is helping people get new apps, not installing ones they manually downloaded. I think this is the use case for AppImageLauncher, which already does everything you want! :) See https://github.com/TheAssassin/AppImageLauncher |
Better Appimage integration would be really good. Appimages are always worse than Flatpaks of course, but sometimes the only option. An integration could look like that: - in Discover you have an "install appimage" button - pressing: - The appimage is made exetueable - A menuentry is created with the directory of the .appimage - and name of the app (has to be extracted but is also shown when running the app) - The menuentry needs to get the icon of the appimage, which is also shown when running it (but dont know where to find it) So making executeable and directing to the path is easy, but extracting icon and name is not so easy maybe. Would make a really great appimage integration though. Maybe the VanillaLinux devs are doing something like that too.