I wanted a nice qt theme to use on Scribus since Arc Dark doesn’t work on there. When I tried to install it, pacman said this will install 50 packages. 300 Mb in total.
Why does a theme need packages such as Kauth and Kwallet?
it’s one of those packages that are only put in the repo with the intent on being itself a dependency of the full kde desktop, since it’s a component of the deskop and not just a random theme
Exactly. Even on Gentoo, which is parsimonious about dependencies, installing breeze pulls in a good chunk of KDE (although you can get just the icons as a separate package). I imagine it includes window decorations and such which need to be compiled against some of the KDE base code, and that’s pulling in everything else.
I’d suggest qt5ct if you’re trying to set up theming for a few QT5 programs on a non-QT5 desktop. It provides a basic GUI for changing colours/fonts/styles/icons rather than a prepackaged theme that may contain more than you want.
Breeze is artwork, styles and assets for the Plasma desktop. I have seen this happen with other distributions as well. I couldn’t tell you why it needs all of those extra bits and pieces.
When you’re not telling us which package you’re trying to install in which packaging system, the only meaningful answer is: you’re trying to install the wrong package.
I’d check that you’re actually installing the most appropriate package. For instance on Ubuntu there’s kid3 which is a MP3 tag application that will pull in the entire k desktop environment. Or you can install kid3-qt which packages its own version of those dependencies and doesn’t pull an entire desktop environment in if you’re using a non-kde environment.
The point is, it’s all self-contained within Flatpak, and won’t slow down and pollute your regular package manager when you’re doing updates, or say you want to grep some package or whatever. More importantly, fewer dependencies == lesser chances of things breaking. And because it’s sandboxed, you don’t need to worry too much about having an older library or whatever that’s needed to work. And in case you want to uninstall it, it’s a fairly clean process, whereas uninstalls via your package manager may not always be clean.
If you use Flatpak from the start, the storage thing becomes less of an issue.
Flatpak only takes considerably more space because people use Flatpak as a last resort or too late into the life of the current installation, as flatpak will have too many requirements for too little apps.
It is accurate that the first few flatpaks will use proportionally more storage as you will need more basic resources but you will will always be using substantially more storage than traditional apps. That said storage is cheap and the correct answer is to buy more instead of choosing tech based on storage requirements.
Yes, but the thing is if you are truly limited by storage, you become paranoid about having to remove old and unused software to free space for the ones you wish to use.
Flatpak offers a benefit on some distros, as you are 100% sure any flatpak can be removed without screwing up with your system. So in a very weird way, the storage increase is worth by knowing you can nuke it if necessary.
flatpak has gtk breeze no the theme for qt apps and in general I don’t see how this would help non flatpak applications which aren’t going to be looking in some flatpak dir for themes.
I don’t enjoy troubleshooting flatpak specific issues when a native package is available personally. Honestly who cares if it pulls in 50 deps if they take in total a few GB when 2TB ssd are cheap.
those “hundreds of deps” are part of your flatpak and you will probably be downloading just as much fortunately fast internet is relatively cheap as is storage space and you probably won’t notice if it takes 15 seconds more.
Normal packaging systems don’t get stuck nor break because you installed more software and its hilarious that you are somehow removing bloat by using a packaging system that calls for you to download the same deps over and over again.
I have 2 flatpaks installed and I already have duplicated runtimes not to speak of the deps themselves that are built into the apps. There is definitely duplication.
If package foo requires runtimev1 and bar requires runtimev1.1 you will end up with installing v1 and v1.1 with similar but not identical files and if another package requires 1.2 and 1.3 and 2.0 then 2.1 eventually you will have a whole lot of libsomethingorother.
Yes because having firefox in /usr/bin/firefox is trashy and disorganized compared to having it in /home/$USER/.var/app/flatpak/app/org.mozilla.firefox/x86_64/stable/6b73214102d2c232a520923fc04166aed89fa52c392b4173ad77d44c1a8fb51b/files/bin/firefox and running firefox is so much more gross than flatpak run org.mozilla.firefox
Normal systems that you don’t do something extremely creative with don’t normally develop conflicts because the packages are literally all designed to work with the same version.
The words " bloating up your actual system and package database." don’t actually mean anything except that you don’t know what any of those words mean together.
I have used countless distros over 20 years including Arch although right now I’m primarily running Void on my personal computers. “Bloating up the package database” remains a meaningless factor because it doesn’t bear meaningfully on real world performance or experience. Your computer doesn’t break more or perform worse because you installed more software because this isn’t windows.
I take 3 seconds looking at what’s updating after I clicked update knowing its incredibly unlikely that anything will break and if it did it would take 30 second to reboot into the snapshot that was automatically created by running the update script.
Add comment