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 part of a thread.
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.
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.
Permanently Deleted
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, that's the entire point - you can have multiple different versions without any conflict.
It also meets any reasonable definition of bloat
The point is, it lives separately to your main installation and doesn't pollute it. It's like putting rubbish in a bin in your room, sure it's still rubbish but it's in the bin so who cares? It's out of sight and doesn't mess up anything else.
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
Can you like actually hear yourself?
Permanently Deleted
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.
Permanently Deleted
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.
- It slows down the update peocess
- It increases the attack surface
- It increases the risk of something breaking due to dependency chains
- It greatly icreases the time you take when you're reviewing all the updates before you update your system
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.