Page MenuHomeSolus

Closed, WontfixPublic



AppImages provide a nice way to users to use applications, alongside flatpack and snaps. While they are simple to use, having low-friction integration is welcome. AppImageLauncher streamlines the process for end-users by: moving them to a dedicated folder, setting the executable bit, and integrating the app into the user's DE ( using .desktop files, etc). This is done with a prompt when clicking an AppImage file for the first time. It also provides dialogs for automated cleanup/removal for AppImages.

While this kind of support for AppImages would be a nice addition to Budgie as first-party support, AppImageLauncher can provide this for Solus users without needing to make any changes to the existing environment.

AppImageLauncher is licensed under the MIT license.

Current source:

Event Timeline

DataDrake closed this task as Wontfix.Feb 9 2019, 8:26 PM
DataDrake added a subscriber: DataDrake.

Closing in favor of appimaged.

@DataDrake, just for clarification, does this mean that there are plans to add appimaged as a default or optional package in the future? I do not currently see it in the repos. I don't particularly care which package is used by solus, just that options for easier AppImage support are available.

@JoshStrobl @DataDrake We should either add appimaged or appimagelauncher.

New AppImages using electron-builder won't provide a Desktop Integration.

More Information:

Best Regards

AppImageLauncher seems to be recommended by electron.

Matf added a subscriber: Matf.EditedMar 6 2020, 5:57 PM

Just curious about this task: it was closed long ago in favor of appimaged but I don't find appimaged in the repository. As @BrowncoatShadow said before, I don't really care about what we have (nor do I have skills to properly compare myself), but I think we should have one. For instance, if using a tiling WM with dmenu to launch applications, appimages won't be integrated in dmenu without appimagelauncher.

Info about this?