In reply to <a href="https://pointieststick.com/2025/10/25/kde-linux-deep-dive-package-management-is-amazing-which-is-why-we-dont-include-it/comment-page-1/#comment-40615">tuxflo</a>. Yeah, I was mostly talking about the "traditional" distros that use package managers based on deb/RPM/pacman, etc. I don't have any experience with Nix, but from what I have seen so far, the technology is as impressive as the user interface to control it is intimidating! 
...
In reply to <a href="https://pointieststick.com/2025/10/25/kde-linux-deep-dive-package-management-is-amazing-which-is-why-we-dont-include-it/comment-page-1/#comment-40617">drew070</a>. About 5.2 GB. See https://files.kde.org/kde-linux/?C=M;O=D...
In reply to <a href="https://pointieststick.com/2025/10/25/kde-linux-deep-dive-package-management-is-amazing-which-is-why-we-dont-include-it/comment-page-1/#comment-40610">aqua</a>. <!-- wp:paragraph --> <p>I'd agree that Kinoite could of been a solid base for KDE Linux</p> <!-- /wp:paragraph --> <!-- wp:list --> <ul class="wp-block-list"><!-- wp:list-item --> <li>Immutable but file-system agnostic</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Vast possibilities for branching (switching between Testing, Unstable, Stable is a matter of rpm-ostree rebase)</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Allows user rebasing to some image from a long time</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Allows usere to arbitrarily pin images (more than 3 if the /boot partition is large enough)</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Allows users to overlay packages (so potentially less hassle with the proprietary stuff) as well as replace image packages</li> <!-- /wp:list-item --></ul> <!-- /wp:list --> <!-- wp:paragraph --> <p>Kinoite has some technical issues though:</p> <!-- /wp:paragraph --> <!-- wp:list --> <ul class="wp-block-list"><!-- wp:list-item --> <li>Relience over RPMFusion for codecs and drivers (yes, even for the AMD hardware). Sometimes RPMFusion packages lag behind mainline, so other packages can't be updated due to conflitcts (which means that the new image can't be built as well)</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Massive package overlaying (e.g., with installing virt-manager) makes system updates VERY slow</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Some Fedora defaults need to be changed for KDE software (e.g., set HISTCONTROL=ignoreboth for the built-in Dolphin terminal)</li> <!-- /wp:list-item --> <!-- wp:list-item --> <li>Need to rebase each year</li> <!-- /wp:list-item --></ul> <!-- /wp:list --> <!-- wp:paragraph --> <p>However, as we've seen with the Universal Blue projects, all these problems can be solved for the user.</p> <!-- /wp:paragraph -->...
<!-- wp:paragraph --> <p>how big is one image if it includes so many things?</p> <!-- /wp:paragraph -->...
<!-- wp:paragraph --> <p>Thanks, I found this both informative and entertaining to read!</p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>I find interesting that you mentioned the Arch base and freeze of the packages. I have some trouble understanding it: would the update cadence be the same as Arch? I wonder this because, for example, the Linux kernel, because I tend to use somewhat older hardware and may not benefit much for the “regular” release. (compared to an LTS kernel, that it's packaged in the Arch repos, if I am not mistaken). But I totally understand the need to support/test newer hardware!</p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>Another reason I pointed out the cadence, was because of the network usage while downloading a new OS image, because in the wiki it mentions about delta updates not being implemented into KDE Linux update mechanism, at the moment. This is one of my main “concerns” with not using package-based distros. (Full disclosure, I use Linux Mint 
so the system updates seems "leaner" and the flatpak updates seems “heavier”, especially runtimes. I do wonder if flatpak/flathubs offer delta updates?)</p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>With that being said, I hope to do a test run of a image-based OS in “real” hardware in a few months.</p> <!-- /wp:paragraph -->...
<!-- wp:quote --> <blockquote><!-- wp:paragraph --> No installation of a package-based operating system can be guaranteed to have the same set of system software and libraries as any other one. <!-- /wp:paragraph --></blockquote> <!-- /wp:quote --> <!-- wp:paragraph --> This isn't true. I don't want to be the "Nix/NixOS fanboy" again, but this is exactly the one reason why nix based package management is superior to all the other stuff. In nix: if it works on my machine, you can be sure that it works on other ones too. <!-- /wp:paragraph -->...