Many distros do their own packaging on their repos, adding dependencies and custom-builds with custom configurations, and this often breaks my OS. On arch, this doesn't happen to me. What's your experience?
However you are right that Arch tries to stay as close as possible to the source. This is fondamentally different than the debian (and thus all debian-derived distros) way of packaging where they aim for a fully integrated OS at the expense of applying their own patches to many packages.
The patches can sometimes bring issues since they can bring unexpected behaviour if you come from Arch and sometimes will help the end user tremendously since they won't have to configure every piece of software to work on their computer.
This is really two way of looking at the issue: Arch is make your own OS and Debian has a more hands off approach.
Custom configs is for people who might not want to tinker as much so maybe it's not for you if you prefer Arch.
To answer the question you asked previously, yes I had issues with custom configs from Debian. One I remember is mupdf being launched by a bash script and thus not understanding why did I have two PIDs (one for bash, one for the mupdf binary) when starting.
For context this was important because I needed to know the PID of mupdf to send a SIGHUP to update the view.
I don't have any issue with Arch, everything works. But when I try other distros, they are mostly messed up.
deleted by creator
Many distros do their own packaging on their repos, adding dependencies and custom-builds with custom configurations, and this often breaks my OS. On arch, this doesn't happen to me. What's your experience?
Arch also does its own packaging on its repos.
However you are right that Arch tries to stay as close as possible to the source. This is fondamentally different than the debian (and thus all debian-derived distros) way of packaging where they aim for a fully integrated OS at the expense of applying their own patches to many packages.
The patches can sometimes bring issues since they can bring unexpected behaviour if you come from Arch and sometimes will help the end user tremendously since they won't have to configure every piece of software to work on their computer.
This is really two way of looking at the issue: Arch is make your own OS and Debian has a more hands off approach.
Yeah.
I know, I said "custom-builds with custom configurations", I mean the custom configurations many distros add.
I also feel like Debian is very clean, but I still miss the big community under Arch, their wiki and AUR…
Custom configs is for people who might not want to tinker as much so maybe it's not for you if you prefer Arch.
To answer the question you asked previously, yes I had issues with custom configs from Debian. One I remember is mupdf being launched by a bash script and thus not understanding why did I have two PIDs (one for bash, one for the mupdf binary) when starting.
For context this was important because I needed to know the PID of mupdf to send a SIGHUP to update the view.