Comment # 6 on bug 1188980 from Josef Reidinger

Reinhard: We discussed this within a team and basically we have ideas how to
fix it, but also we would like to verify it with you as you introduce that
branding pools packages.

So installation use-cases:

1. user wants distro defaults. In such case I think it makes sense to ensure
that branding pool is installed ( so force install of chrony-pool-nonempty )
and ensure that chrony service is enabled and do nothing beside that.

2. user wants his own ntp server to be used. In such case we should force
chrony-pool-empty and write to /etc/chrony.d/pool.conf server user wants to
use.

3. user do not want ntp sync - in such case do not install chrony.

And second case is modifications on running system. Reading is easy case as we
can read all entries and read pool from it, but big topic is how to handle
changes. What do you recommend to do? Remove pool keys from all configs and
just use pool.conf? or disable touching of pools outside of pool.conf? And what
about old chrony config in chrony.conf when user migrate?