this post was submitted on 03 Nov 2024
113 points (99.1% liked)

Linux

5222 readers
122 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] FizzyOrange@programming.dev -1 points 1 week ago (3 children)

Hmmm I guess this kind of makes sense - most distros push Gnome above KDE (probably because it doesn't look like this - where's Tantacrul when you need him?). On the other hand, there's already Kubuntu...

I'm a bit skeptical about immutable distros too. What if I want to install a package that isn't already installed and isn't available as a Flatpak/Snap? Seems like it's going to run in similar issues to everything else that tries to wade upstream against the bad decisions of the existing Linux packaging zeitgeist, e.g. how Nix has to install everything in one root-owned directory because nobody cares about portable installation.

[–] e8d79@discuss.tchncs.de 2 points 1 week ago* (last edited 1 week ago) (2 children)

What if I want to install a package that isn’t already installed and isn’t available as a Flatpak/Snap?

Then you just layer it.

[–] FizzyOrange@programming.dev 1 points 1 week ago (1 children)

Interesting, so that's sort of customising the image somehow? Does it use an overlay FS or something?

[–] e8d79@discuss.tchncs.de 1 points 1 week ago

The silverblue docs explain it best:

When a package is installed with rpm-ostree, a new OS image is composed by adding the RPM payload to the existing OS image, and creating a new, combined image.