this post was submitted on 06 Nov 2024
338 points (99.4% liked)
Linux
48152 readers
774 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.