Hi Paul, sorry for the late answer, but better late than never...
As the bug title says, those recommendations are best practices and for me there is no need to put them into policy. There can always be good reasons to not use dbconfig-common at all (it just can't be as flexible as required to meet all the different scenarios) and therefore it won't be desirable to put any pressure on maintainers of database applications to use it. Nevertheless a good best paractices section like [1] with hints to various examples is highly appreciated and will be sufficient. Just my 2¢, Mathias [1] https://www.debian.org/doc/manuals/dbapp-policy/ch-dbapps.html -- Mathias Behrle ✧ Debian Developer PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
