pin Don't use pacman, that runs on Arch.
I heard that it is used in PacBSD.
pin I use pkgin and xbps 😉
Are there various packages available?
pin But, no. Usually the package manager is smart enough and checks if the dependency has already been pulled by another package that requires it and its present in your system. That dependency then become shared and if you'd remove it, it would break all packages depending on it, not just the one that pulled it in as a dependency in the first place.
I see, so that means that flatpak, snap and appimage all just download the exact same packages rather than sharing the packages amongst the applications that uses the same dependencies?
pin Pulling multiple copies of the same library, or any other dependency for that matter, its a Windows thing.
Oh I see, this is why Windows doesn't suffer from dependency hell.
pin That depends on the philosophy of the OS. and if proprietary software can still be installed. We're talking closed source binaries here, right?
Proprietary means human readable code being closed source, right?
pin I think, for open source applications, chances are that there're many more eyeballs looking at the code if the software is distributed through the official package repos, than it would be if coming from a third party repo like flathub.
But wouldn't it be the same regardless of where it is being distributed from? Cause like for example with Firefox, it could be distributed from pacman and from flatpak, wouldn't the source code be the same?
pin AUR is, for obvious reasons, excluded here.
I keep getting confused with this, AUR is another package manager like pacman?
pin I'm not telling you not to use them, I just think its wrong.
I think you got some very interesting reasons as to why to not use flatpak and other stuff. Does appimage share all the dependencies together?