<!-- wp:paragraph --> <p>Well that was clever. I saw the "login to post" note below, so tried to, and waddya know, it posted my half finished post. </p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>To continue, I would prefer at least the option of being able to select what gets installed. I don't use many programs. Browser, email, office suite, spotify, couple of other bits and pieces but that's about it. I don't need five browsers and three email programs and four music players. I don't need a paint program. Please, let me choose what to install. The alternative is to spend hours getting rid of everything I don't want, and yes, sometimes deleting things that stop other things that I do want from working. </p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>I'm not particularly technical, I'm more of your bog standard end user. For the record I like Discover. It suits me fine. I will use a GUI, if there is one, over the command line, but happy to use the command line as well. I like flatpaks, they make a lot of sense to me, especially when used in conjunction with an "immutable" distro. I like the idea of an immutable distro and have experimented with a couple. I never found a need to layer anything into the base system though, and don't really understand why anybody would want to, but I'm assuming there must be important use cases of which I am blissfully unaware. I will use an appimage if there is no flatpak. I won't use a snap. </p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>Just my two cents worth.</p> <!-- /wp:paragraph -->...
<!-- wp:paragraph --> <p>One of the things I don't like about linuxes is the "everything is included" concept. I don't need every language installed. I only speak one, English, so everything else is waste of space. I don't need ten thousand fonts. I don't need every single Plasma app. </p> <!-- /wp:paragraph -->...
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 -->...
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-40613">river</a>. I don't think KDE Linux is going to kill off Debian, Ubuntu, openSUSE, Fedora, Gentoo, etc. The idea is to provide a more vertically integrated product for those who want that. There's demand from OEMs and institutions who like what KDE is doing, and a need with KDE neon fading out...
Forgive me for asking the obvious question but what's the end goal here for KDE Linux? Be a general purpose Linux distribution of KDE/Plasma flavor in opposition to Gnome one? If these are the plans for both projects then what will happen to other distributions? Will we'll be slowly heading towards some bipolar homogenization of Linux world? For quite some time I'm having this weird feeling that Gnome tries to appeal to business world by hands of people within the project who willingly or not are pushing all this simplified approach to the interface. People in various places online are also pointing out that this community acts in a really hostile way towards ordinary users and feedback they're giving. So again, what's your plans? Be another flavor people could pick from or something bigger?...