Am 16.04.2018 um 19:17 schrieb Michael Biebl: > Maybe the best we can do is to document in README.Debian, that users of > an alternative NTP client, have to disable systemd-timesyncd manually. > The Condition is only a hack and I'd rather not add it back. It's not a > proper solution either, as it only checks for the existince of the > binaries, not if the alternative NTP services are actually running.
The only other alternative I can think of, is splitting systemd-timesyncd into a separate package, which has Conflicts/Replaces/Provides: time-daemon But that will open another can of worms. First of all, I'm not too thrilled having a separate binary package for a 44K binary. Second, we want to have systemd-timesyncd installed and enabled by default. A Recommends will not cut, as systemd is installed during early debootstrap, where Recommends are not considered. There might also be the risk, that by adding a Recommends, we trigger the uninstallation of any already installed alternative, like ntp, which would most likely not make people happy. If we don't add a Recommends though, people without having installed another alternative would suddenly not have systemd-timesyncd anymore, so we'd create a regression as well. So, I'm not sure if any changes to the status quo actually improve the current situation, but I'm open to other ideas. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
