Why does the breeze theme have 50 dependencies?
Why does the breeze theme have 50 dependencies?
(This is a half-rant half actual question)
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?
You're viewing a single thread.
This is one of those areas where Flatpak shines - install the Flatpak versions of Scribus and Breeze, and keep your system free from unwanted package bloat.
I would use Flatpak more often if I had the money for more storage space :(
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.
If it’s packaged right, Breeze is gonna need those 50 dependencies whether it’s in Flatpak or not.
Doesn't matter, the point is your dependencies are contained within Flatpak and won't pollute your main package manager.
And what do you get from that?
More bloat from flatpak overhead :^)
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.
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.
Permanently Deleted
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.
It's not about the size at all, it's about the maintenance overhead and pollution of the main package system database. I don't want to see hundreds of junk dependencies getting updated and slowing down my update run, just for the sake of a single infrequently used app. Then you also run into the potential issue of something breaking and you're left scratching your head wondering what this dependency does and why it's installed in the first place. Or maybe one of the dependencies conflicts with something else. It's just a pleasant situation at all.
I don't enjoy troubleshooting flatpak specific issues
Me neither, so I'll weigh the pros and cons. If it means installing hundreds of dependencies for a app that I'm not going to use frequently and no other app is using that dependency, then it may be worthwhile. At least, there's no harm in trying the Flatpak first, afterall, its clean and self-contained and if it's not working out for you, you can get rid of it quite easily.
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.
Permanently Deleted
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.
Having a complex dependency chain can and does break things at times, forcing you to make a choice - either downgrade something or remove the conflicting package. Why unnecessary create conflicts for yourself?
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.
You clearly don't know how Flatpak works - you're not downloading the same deps over and over, at least not for common/platform deps like what's needed for KDE/Qt apps to work. And my original point remains, which is you're not bloating up your actual system and package database.
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.