Can’t wait, it’s becoming really usable (I always needed adjustment layers, and it now mostly has them). I wish they offered an appimage though, I’m not big on flatpaks due to size.
I was also wondering about this. Flatpaks apparently come with more libraries to interact with other Flatpaks, whereas AppImages tend be purely app-specific and their libraries are compressed for their usage only.
Flatpak doesn’t come with more libraries to interact with other flatpaks. It comes with libraries that the application’s flatpak you’re downloading requires. However, when installing the flatpak those libraries do not get installed if they are already on the system.
So widget-flatpak needs lib-a and lib-b. You’re system already has lib-b that flatpak is using for as another flatpak.
You install widget-flatpak. lib-a gets installed but lib-b does not because you already have it.
There’s third party Appimages. They also had a blog post discussing using Appimages for testing builds. If that gets done, I don’t see why they wouldn’t offer an official build.
In the release blog they mentioned working on appimage. Right now they are only using it for testing purposes and it should be compatbible with Debian. But there is no “official” distribution as of now.
Can’t wait, it’s becoming really usable (I always needed adjustment layers, and it now mostly has them). I wish they offered an appimage though, I’m not big on flatpaks due to size.
Appimage doesn’t do deduplication where possible like Flatpak does, where did you get the idea that Flatpak packages are bigger?
I was also wondering about this. Flatpaks apparently come with more libraries to interact with other Flatpaks, whereas AppImages tend be purely app-specific and their libraries are compressed for their usage only.
Flatpak doesn’t come with more libraries to interact with other flatpaks. It comes with libraries that the application’s flatpak you’re downloading requires. However, when installing the flatpak those libraries do not get installed if they are already on the system.
So widget-flatpak needs lib-a and lib-b. You’re system already has lib-b that flatpak is using for as another flatpak.
You install widget-flatpak. lib-a gets installed but lib-b does not because you already have it.
It’s about time, after like 20 years.
There’s third party Appimages. They also had a blog post discussing using Appimages for testing builds. If that gets done, I don’t see why they wouldn’t offer an official build.
In the release blog they mentioned working on appimage. Right now they are only using it for testing purposes and it should be compatbible with Debian. But there is no “official” distribution as of now.