Comment 3 for bug 1778911

Currently we have these:
Reverse-Recommends
==================
* ceph-base (for chrony)

This is the same case as with Freeipa.

* radioclk (for chrony)

This is meant to provide DCF77 input to chrony, so ok

Reverse-Depends
===============
* freeipa-client (for chrony)
* freeipa-server (for chrony)

This is how this bug was reported.
I think it is a common and working resolution to depend on the current timeserver.
I'd vote for the Depends becoming recommends so that admins can remove the package if wanted.

* gce-compute-image-packages (for chrony)

That is an intentional "there you should sync with that" AFAIK. keeping as-is IMHO

* maas-rack-controller (for chrony)
* maas-region-api (for chrony)

I know for MAAS that they really want this, even on a Container, so considering them ok'ish.
They even modify chrony.conf and such, so there a depends is correct.

In general I think the Ceph approach is good, keeping it as a recommends allows to remove it if needed. BTW Chrony on Containers will by default only serve the local time as syncing it would not work (CAP_SYS_TIME) anyway - so not much lost.

systemd-timesyncd is "only" SNTP which has to be considered inferior to full ntp syncing.

For Ceph and Freeipa once being a recommends, I'd wish there would be a dependency that says "but not in containers", but there is none.