3 ms·
systemd plays a crucial role on systems that use it. Whoever builds systemd for a distribution should definitely be aware of those flags; if you don’t understan
by ckastner 6y ago
systemd plays a crucial role on systems that use it. Whoever builds systemd for a distribution should definitely be aware of those flags; if you don’t understand them, then you are not qualified sufficiently to ship systemd for others to use.
Edit: Speaking as a package maintainer myself.
- falcolas 6y agoHow many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases? I expect that package maintainers are human, and put a fair bit of trust in the upstream developers, and will only tinker with build flags for issues which are specific to the distro. I also expect that they will miss changes to defaults, or new flags, or deprecated flags, quite often. I looked at the systemd defaults to see this issue for myself, and the fact that Google's nameservers are in the DNS defaults didn't immediately pop out to me (it's a list of 8 mixed IPv4 and IPv6 addresses).
- ckastner 6y ago> How many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases? Absolutely. For a responsible package maintainer, reading changelogs and release notes of new releases is a must. For sensitive software (eg: key system libraries), I usually also look at the full diff between releases. I also run tests with dependent software before uploading my version, lest I break any packages that depend on mine. etc. And this is quite typical of your average distribution package maintainer.
- falcolas 6y agoFair enough - thank you!
- deleted 6y ago[deleted]