#appimages — Public Fediverse posts

Wie verwaltest Du deine #AppImages unter #Linux? Ist es bei Dir eher ein Durcheinander als organisiert?

✍️ Zu diesem Thema habe ich einen kurzen Blogbeitrag verfasst.

🔗 https://testorakel.de/blog/endlich-ordnung-im-appimage-chaos

#AppImage

Wie verwaltest Du deine #AppImages unter #Linux? Ist es bei Dir eher ein Durcheinander als organisiert?

✍️ Zu diesem Thema habe ich einen kurzen Blogbeitrag verfasst.

🔗 https://testorakel.de/blog/endlich-ordnung-im-appimage-chaos

#AppImage

Wie verwaltest Du deine #AppImages unter #Linux? Ist es bei Dir eher ein Durcheinander als organisiert?

✍️ Zu diesem Thema habe ich einen kurzen Blogbeitrag verfasst.

🔗 https://testorakel.de/blog/endlich-ordnung-im-appimage-chaos

#AppImage

@itsfoss hi! Are you aware of the #PkgForge project? 👀

They are trying to do a lot of cool stuff with AppImages, by making them actually universal and compatible with as many versions and variations of Linux desktop as reasonably possible.

For example, the fuse issue isn't a problem with these because the uruntime automatically falls back to namespaces based execution which falls back to the extract and run mode that appimages support! This, along with the care they take to ensure everything is as universal as possible makes me want to use their work a lot.

I recognize that a lot of people are turned off by #AppImages because of the things probonopd has said in the past so I have to emphasize: I think most(if not all?) of the stack has been rewritten and has no real influence of probonopd here.

For example, uruntime is written in rust and I've seen the team go above and beyond for stuff like fixing Wayland support, both of which probonopd seems to have a grudge against...? Lol

Disclaimer: I am a little biased as I did a package for them a year or two ago :blobcatfingerguns:

https://pkgforge-dev.github.io/Anylinux-AppImages/

I get that not all AppImages are made this way but I feel like the more people who know about this, the better smaller projects feel empowered to give modern AppImages another chance, especially because of all the bad press around AppImages :sad_panda:

@itsfoss hi! Are you aware of the #PkgForge project? 👀

They are trying to do a lot of cool stuff with AppImages, by making them actually universal and compatible with as many versions and variations of Linux desktop as reasonably possible.

For example, the fuse issue isn't a problem with these because the uruntime automatically falls back to namespaces based execution which falls back to the extract and run mode that appimages support! This, along with the care they take to ensure everything is as universal as possible makes me want to use their work a lot.

I recognize that a lot of people are turned off by #AppImages because of the things probonopd has said in the past so I have to emphasize: I think most(if not all?) of the stack has been rewritten and has no real influence of probonopd here.

For example, uruntime is written in rust and I've seen the team go above and beyond for stuff like fixing Wayland support, both of which probonopd seems to have a grudge against...? Lol

Disclaimer: I am a little biased as I did a package for them a year or two ago :blobcatfingerguns:

https://pkgforge-dev.github.io/Anylinux-AppImages/

I get that not all AppImages are made this way but I feel like the more people who know about this, the better smaller projects feel empowered to give modern AppImages another chance, especially because of all the bad press around AppImages :sad_panda:

@itsfoss hi! Are you aware of the #PkgForge project? 👀

They are trying to do a lot of cool stuff with AppImages, by making them actually universal and compatible with as many versions and variations of Linux desktop as reasonably possible.

For example, the fuse issue isn't a problem with these because the uruntime automatically falls back to namespaces based execution which falls back to the extract and run mode that appimages support! This, along with the care they take to ensure everything is as universal as possible makes me want to use their work a lot.

I recognize that a lot of people are turned off by #AppImages because of the things probonopd has said in the past so I have to emphasize: I think most(if not all?) of the stack has been rewritten and has no real influence of probonopd here.

For example, uruntime is written in rust and I've seen the team go above and beyond for stuff like fixing Wayland support, both of which probonopd seems to have a grudge against...? Lol

Disclaimer: I am a little biased as I did a package for them a year or two ago :blobcatfingerguns:

https://pkgforge-dev.github.io/Anylinux-AppImages/

I get that not all AppImages are made this way but I feel like the more people who know about this, the better smaller projects feel empowered to give modern AppImages another chance, especially because of all the bad press around AppImages :sad_panda:

@itsfoss hi! Are you aware of the #PkgForge project? 👀

They are trying to do a lot of cool stuff with AppImages, by making them actually universal and compatible with as many versions and variations of Linux desktop as reasonably possible.

For example, the fuse issue isn't a problem with these because the uruntime automatically falls back to namespaces based execution which falls back to the extract and run mode that appimages support! This, along with the care they take to ensure everything is as universal as possible makes me want to use their work a lot.

I recognize that a lot of people are turned off by #AppImages because of the things probonopd has said in the past so I have to emphasize: I think most(if not all?) of the stack has been rewritten and has no real influence of probonopd here.

For example, uruntime is written in rust and I've seen the team go above and beyond for stuff like fixing Wayland support, both of which probonopd seems to have a grudge against...? Lol

Disclaimer: I am a little biased as I did a package for them a year or two ago :blobcatfingerguns:

https://pkgforge-dev.github.io/Anylinux-AppImages/

I get that not all AppImages are made this way but I feel like the more people who know about this, the better smaller projects feel empowered to give modern AppImages another chance, especially because of all the bad press around AppImages :sad_panda:

@itsfoss hi! Are you aware of the #PkgForge project? 👀

They are trying to do a lot of cool stuff with AppImages, by making them actually universal and compatible with as many versions and variations of Linux desktop as reasonably possible.

For example, the fuse issue isn't a problem with these because the uruntime automatically falls back to namespaces based execution which falls back to the extract and run mode that appimages support! This, along with the care they take to ensure everything is as universal as possible makes me want to use their work a lot.

I recognize that a lot of people are turned off by #AppImages because of the things probonopd has said in the past so I have to emphasize: I think most(if not all?) of the stack has been rewritten and has no real influence of probonopd here.

For example, uruntime is written in rust and I've seen the team go above and beyond for stuff like fixing Wayland support, both of which probonopd seems to have a grudge against...? Lol

Disclaimer: I am a little biased as I did a package for them a year or two ago :blobcatfingerguns:

https://pkgforge-dev.github.io/Anylinux-AppImages/

I get that not all AppImages are made this way but I feel like the more people who know about this, the better smaller projects feel empowered to give modern AppImages another chance, especially because of all the bad press around AppImages :sad_panda:

Troubleshooting " #AppImages require #FUSE to run " on #Linux

https://itsfoss.com/appimage-fuse-issue/

Troubleshooting " #AppImages require #FUSE to run " on #Linux

https://itsfoss.com/appimage-fuse-issue/

Troubleshooting " #AppImages require #FUSE to run " on #Linux

https://itsfoss.com/appimage-fuse-issue/

Troubleshooting " #AppImages require #FUSE to run " on #Linux

https://itsfoss.com/appimage-fuse-issue/

Troubleshooting " #AppImages require #FUSE to run " on #Linux

https://itsfoss.com/appimage-fuse-issue/

@signalapp is looking for feedback on the new #Linux installation method! But am I the only one who thinks #AppImages are like the worst choice? 😭

https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/

@signalapp is looking for feedback on the new #Linux installation method! But am I the only one who thinks #AppImages are like the worst choice? 😭

https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/

@signalapp is looking for feedback on the new #Linux installation method! But am I the only one who thinks #AppImages are like the worst choice? 😭

https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/

@signalapp is looking for feedback on the new #Linux installation method! But am I the only one who thinks #AppImages are like the worst choice? 😭

https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/

@signalapp is looking for feedback on the new #Linux installation method! But am I the only one who thinks #AppImages are like the worst choice? 😭

https://community.signalusers.org/t/beta-test-the-signal-desktop-linux-appimage/

Let me underline again: #Ubuntu and #Snap is just another #WalledGarden, another attempt at encircling #Linux in a way to co-opt #libre software. #uutils is just another step.

At this point, I'll have to remind people that systems such as #NixOS exist, or that you can pretty much isolate and sandbox apps and services in many ways.

But the difference with Ubuntu is how you have to jump through hoops to get things like #AppImages and #Flatpak to work - and that's by design.

Let me underline again: #Ubuntu and #Snap is just another #WalledGarden, another attempt at encircling #Linux in a way to co-opt #libre software. #uutils is just another step.

At this point, I'll have to remind people that systems such as #NixOS exist, or that you can pretty much isolate and sandbox apps and services in many ways.

But the difference with Ubuntu is how you have to jump through hoops to get things like #AppImages and #Flatpak to work - and that's by design.

Let me underline again: #Ubuntu and #Snap is just another #WalledGarden, another attempt at encircling #Linux in a way to co-opt #libre software. #uutils is just another step.

At this point, I'll have to remind people that systems such as #NixOS exist, or that you can pretty much isolate and sandbox apps and services in many ways.

But the difference with Ubuntu is how you have to jump through hoops to get things like #AppImages and #Flatpak to work - and that's by design.

Let me underline again: #Ubuntu and #Snap is just another #WalledGarden, another attempt at encircling #Linux in a way to co-opt #libre software. #uutils is just another step.

At this point, I'll have to remind people that systems such as #NixOS exist, or that you can pretty much isolate and sandbox apps and services in many ways.

But the difference with Ubuntu is how you have to jump through hoops to get things like #AppImages and #Flatpak to work - and that's by design.

Let me underline again: #Ubuntu and #Snap is just another #WalledGarden, another attempt at encircling #Linux in a way to co-opt #libre software. #uutils is just another step.

At this point, I'll have to remind people that systems such as #NixOS exist, or that you can pretty much isolate and sandbox apps and services in many ways.

But the difference with Ubuntu is how you have to jump through hoops to get things like #AppImages and #Flatpak to work - and that's by design.

KDE Linux Distribution Is Available for Public Testing, Download Now - 9to5Linux

...interessanter Ansatz des KDE-Projektes eine Referenz-Distro auf die Beine zustellen.

https://9to5linux.com/kde-linux-distribution-is-available-for-public-testing-download-now

Weitere Links:
https://kde.org/linux/
https://linuxnews.de/kde-linux-als-fruehes-test-image/

#KDElinux #PublicTesting #KDEneon #Archbased #FlatpakApps #AppImages #Alpha #Btrfs

KDE Linux Distribution Is Available for Public Testing, Download Now - 9to5Linux

...interessanter Ansatz des KDE-Projektes eine Referenz-Distro auf die Beine zustellen.

https://9to5linux.com/kde-linux-distribution-is-available-for-public-testing-download-now

Weitere Links:
https://kde.org/linux/
https://linuxnews.de/kde-linux-als-fruehes-test-image/

#KDElinux #PublicTesting #KDEneon #Archbased #FlatpakApps #AppImages #Alpha #Btrfs

KDE Linux Distribution Is Available for Public Testing, Download Now - 9to5Linux

...interessanter Ansatz des KDE-Projektes eine Referenz-Distro auf die Beine zustellen.

https://9to5linux.com/kde-linux-distribution-is-available-for-public-testing-download-now

Weitere Links:
https://kde.org/linux/
https://linuxnews.de/kde-linux-als-fruehes-test-image/

#KDElinux #PublicTesting #KDEneon #Archbased #FlatpakApps #AppImages #Alpha #Btrfs

Since our switch from Ubuntu 22.04 LTS to 24.04 LTS as the base for TUXEDO OS, some customers have reported that certain AppImages no longer start. We investigated the issue and were able to reproduce it generally for Ubuntu 24.04 LTS and all operating systems based on it. We found that it affects only AppImages built on Electron. The AppImage of our own TUXEDO WebFAI Creator is also impacted.

You can find the full article here: https://www.tuxedocomputers.com/en/Some-AppImages-wont-start-What-can-I-do.tuxedo

#article #appimages #linux

Since our switch from Ubuntu 22.04 LTS to 24.04 LTS as the base for TUXEDO OS, some customers have reported that certain AppImages no longer start. We investigated the issue and were able to reproduce it generally for Ubuntu 24.04 LTS and all operating systems based on it. We found that it affects only AppImages built on Electron. The AppImage of our own TUXEDO WebFAI Creator is also impacted.

You can find the full article here: https://www.tuxedocomputers.com/en/Some-AppImages-wont-start-What-can-I-do.tuxedo

#article #appimages #linux

I had a fantastic experiance last week using #claude (#claude_code specifically) to generate a script that helps me install #appimages on my #Fedora desktop. Appimages are these weird files that don't seem to play nicely with the package managers we know and love. They require manually moving to a directory and then creating a .desktop file so that your launcher (#rofi in my case) can find it.

The resulting script here: https://github.com/vitallish/dotfiles/blob/main/.config/scripts/install_appimage

Seems to work with #Beeper!

I had a fantastic experiance last week using #claude (#claude_code specifically) to generate a script that helps me install #appimages on my #Fedora desktop. Appimages are these weird files that don't seem to play nicely with the package managers we know and love. They require manually moving to a directory and then creating a .desktop file so that your launcher (#rofi in my case) can find it.

The resulting script here: https://github.com/vitallish/dotfiles/blob/main/.config/scripts/install_appimage

Seems to work with #Beeper!

I had a fantastic experiance last week using #claude (#claude_code specifically) to generate a script that helps me install #appimages on my #Fedora desktop. Appimages are these weird files that don't seem to play nicely with the package managers we know and love. They require manually moving to a directory and then creating a .desktop file so that your launcher (#rofi in my case) can find it.

The resulting script here: https://github.com/vitallish/dotfiles/blob/main/.config/scripts/install_appimage

Seems to work with #Beeper!

In Ubuntu, again, Appimages are not launching. This time it's the 25.04 release and none of the fixes for previous releases are working. I've even checked AppArmor to ensure the Appimage in question isn't being blocked from running for some reason. Why does this issue continue in Ubuntu releases when so many have reported the issue? My son, just yesterday, got fed up with the issue and moved to openSUSE on his laptop and desktop. My neighbor, who I convinced to move to Linux just a year ago from Windows, is also looking to move to a different distribution or, sadly, even back to Windows. Is this simply Ubuntu making it difficult to run anything but Snaps? I'm sure this isn't the reason but I am sure that many are thinking this. There have been multiple users asking about this in the Ubuntu Discourse but the posts are being locked from zero activity. And please, I don't want to hear your thoughts on how bad Appimages are or something. Many people use them, myself included. I like them.

Ubuntu and Canonical, I love you, but you need to get it together. This is just ridiculous.

#ubuntu #linux #appimages

In Ubuntu, again, Appimages are not launching. This time it's the 25.04 release and none of the fixes for previous releases are working. I've even checked AppArmor to ensure the Appimage in question isn't being blocked from running for some reason. Why does this issue continue in Ubuntu releases when so many have reported the issue? My son, just yesterday, got fed up with the issue and moved to openSUSE on his laptop and desktop. My neighbor, who I convinced to move to Linux just a year ago from Windows, is also looking to move to a different distribution or, sadly, even back to Windows. Is this simply Ubuntu making it difficult to run anything but Snaps? I'm sure this isn't the reason but I am sure that many are thinking this. There have been multiple users asking about this in the Ubuntu Discourse but the posts are being locked from zero activity. And please, I don't want to hear your thoughts on how bad Appimages are or something. Many people use them, myself included. I like them.

Ubuntu and Canonical, I love you, but you need to get it together. This is just ridiculous.

#ubuntu #linux #appimages

In Ubuntu, again, Appimages are not launching. This time it's the 25.04 release and none of the fixes for previous releases are working. I've even checked AppArmor to ensure the Appimage in question isn't being blocked from running for some reason. Why does this issue continue in Ubuntu releases when so many have reported the issue? My son, just yesterday, got fed up with the issue and moved to openSUSE on his laptop and desktop. My neighbor, who I convinced to move to Linux just a year ago from Windows, is also looking to move to a different distribution or, sadly, even back to Windows. Is this simply Ubuntu making it difficult to run anything but Snaps? I'm sure this isn't the reason but I am sure that many are thinking this. There have been multiple users asking about this in the Ubuntu Discourse but the posts are being locked from zero activity. And please, I don't want to hear your thoughts on how bad Appimages are or something. Many people use them, myself included. I like them.

Ubuntu and Canonical, I love you, but you need to get it together. This is just ridiculous.

#ubuntu #linux #appimages

In Ubuntu, again, Appimages are not launching. This time it's the 25.04 release and none of the fixes for previous releases are working. I've even checked AppArmor to ensure the Appimage in question isn't being blocked from running for some reason. Why does this issue continue in Ubuntu releases when so many have reported the issue? My son, just yesterday, got fed up with the issue and moved to openSUSE on his laptop and desktop. My neighbor, who I convinced to move to Linux just a year ago from Windows, is also looking to move to a different distribution or, sadly, even back to Windows. Is this simply Ubuntu making it difficult to run anything but Snaps? I'm sure this isn't the reason but I am sure that many are thinking this. There have been multiple users asking about this in the Ubuntu Discourse but the posts are being locked from zero activity. And please, I don't want to hear your thoughts on how bad Appimages are or something. Many people use them, myself included. I like them.

Ubuntu and Canonical, I love you, but you need to get it together. This is just ridiculous.

#ubuntu #linux #appimages

In Ubuntu, again, Appimages are not launching. This time it's the 25.04 release and none of the fixes for previous releases are working. I've even checked AppArmor to ensure the Appimage in question isn't being blocked from running for some reason. Why does this issue continue in Ubuntu releases when so many have reported the issue? My son, just yesterday, got fed up with the issue and moved to openSUSE on his laptop and desktop. My neighbor, who I convinced to move to Linux just a year ago from Windows, is also looking to move to a different distribution or, sadly, even back to Windows. Is this simply Ubuntu making it difficult to run anything but Snaps? I'm sure this isn't the reason but I am sure that many are thinking this. There have been multiple users asking about this in the Ubuntu Discourse but the posts are being locked from zero activity. And please, I don't want to hear your thoughts on how bad Appimages are or something. Many people use them, myself included. I like them.

Ubuntu and Canonical, I love you, but you need to get it together. This is just ridiculous.

#ubuntu #linux #appimages

The more I look into something like #Snap from Canonical, the less I like it. I am old school, but that isn't the reason. I understand the idea behind global type packages like #Flatpak, #AppImages, and even #Snap. I just hate the way Canonical has gone so heavy-handed on it, pirating apt cmds, and closed off the back-end. Just seems to be anti-FOSS. I no others disagree and that is fine. Just my personal take.

The more I look into something like #Snap from Canonical, the less I like it. I am old school, but that isn't the reason. I understand the idea behind global type packages like #Flatpak, #AppImages, and even #Snap. I just hate the way Canonical has gone so heavy-handed on it, pirating apt cmds, and closed off the back-end. Just seems to be anti-FOSS. I no others disagree and that is fine. Just my personal take.

The more I look into something like #Snap from Canonical, the less I like it. I am old school, but that isn't the reason. I understand the idea behind global type packages like #Flatpak, #AppImages, and even #Snap. I just hate the way Canonical has gone so heavy-handed on it, pirating apt cmds, and closed off the back-end. Just seems to be anti-FOSS. I no others disagree and that is fine. Just my personal take.

The more I look into something like #Snap from Canonical, the less I like it. I am old school, but that isn't the reason. I understand the idea behind global type packages like #Flatpak, #AppImages, and even #Snap. I just hate the way Canonical has gone so heavy-handed on it, pirating apt cmds, and closed off the back-end. Just seems to be anti-FOSS. I no others disagree and that is fine. Just my personal take.

The more I look into something like #Snap from Canonical, the less I like it. I am old school, but that isn't the reason. I understand the idea behind global type packages like #Flatpak, #AppImages, and even #Snap. I just hate the way Canonical has gone so heavy-handed on it, pirating apt cmds, and closed off the back-end. Just seems to be anti-FOSS. I no others disagree and that is fine. Just my personal take.

Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!

On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 😛

Something that would be really nice to add to #KDE and Kinoite is a section in Application Permissions for managing #AppImages

Basically everything they do for #Flatpak but in AppImage terms. Gear Level essentially. They already have a (imo superfluous) subsection for X11, let's expand it while we're at it

No they aren't exactly sandboxed the way Flatpaks are so the perms might not work the same, but an integrated menu to manage them would go a long way.
More integrations for managing packages of all types would be good actually

I want to right click a desktop shortcut to a flatpak, appimage or snap and get a menu that links to the Permissions page

I want to open the Permissions page and get an About info screen and a 1-click uninstall button instead of sending me to Discover. Why are you sending me to Discover? What if its not listed in Discover?

I want to double click an RPM, DEB or .desktop and have that give me options for installing that to my native package store, distro/toolbox or rpm-ostree

Something that would be really nice to add to #KDE and Kinoite is a section in Application Permissions for managing #AppImages

Basically everything they do for #Flatpak but in AppImage terms. Gear Level essentially. They already have a (imo superfluous) subsection for X11, let's expand it while we're at it

No they aren't exactly sandboxed the way Flatpaks are so the perms might not work the same, but an integrated menu to manage them would go a long way.
More integrations for managing packages of all types would be good actually

I want to right click a desktop shortcut to a flatpak, appimage or snap and get a menu that links to the Permissions page

I want to open the Permissions page and get an About info screen and a 1-click uninstall button instead of sending me to Discover. Why are you sending me to Discover? What if its not listed in Discover?

I want to double click an RPM, DEB or .desktop and have that give me options for installing that to my native package store, distro/toolbox or rpm-ostree

Something that would be really nice to add to #KDE and Kinoite is a section in Application Permissions for managing #AppImages

Basically everything they do for #Flatpak but in AppImage terms. Gear Level essentially. They already have a (imo superfluous) subsection for X11, let's expand it while we're at it

No they aren't exactly sandboxed the way Flatpaks are so the perms might not work the same, but an integrated menu to manage them would go a long way.
More integrations for managing packages of all types would be good actually

I want to right click a desktop shortcut to a flatpak, appimage or snap and get a menu that links to the Permissions page

I want to open the Permissions page and get an About info screen and a 1-click uninstall button instead of sending me to Discover. Why are you sending me to Discover? What if its not listed in Discover?

I want to double click an RPM, DEB or .desktop and have that give me options for installing that to my native package store, distro/toolbox or rpm-ostree

Something that would be really nice to add to #KDE and Kinoite is a section in Application Permissions for managing #AppImages

Basically everything they do for #Flatpak but in AppImage terms. Gear Level essentially. They already have a (imo superfluous) subsection for X11, let's expand it while we're at it

No they aren't exactly sandboxed the way Flatpaks are so the perms might not work the same, but an integrated menu to manage them would go a long way.
More integrations for managing packages of all types would be good actually

I want to right click a desktop shortcut to a flatpak, appimage or snap and get a menu that links to the Permissions page

I want to open the Permissions page and get an About info screen and a 1-click uninstall button instead of sending me to Discover. Why are you sending me to Discover? What if its not listed in Discover?

I want to double click an RPM, DEB or .desktop and have that give me options for installing that to my native package store, distro/toolbox or rpm-ostree