Package: dbconfig-common Followup-For: Bug #476946 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Discussing this bug on the BSP in Utrecht [1], we were wondering if this issue could not be fixed by parsing the configuration file if it exists (and using that with higher) priority than the debconf values). If the file does not exist you can then just use the debconf values, regardless of whether they come from preseeding or not. An example of such a scheme is in the pioneers-meta-server package. We will file a wishlist bug on debconf to offer parsing of configuration files, similar to the functionality in pioneers-meta-server. [1] http://wiki.debian.org/BSP/2012/10/nl/Utrecht -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlB5gbUACgkQHNUte6r+CGqbmgCfbOsaqWHw27F0kmjLFdl+7Vdb 5/cAnin8hu0wY75LxByLG9FbmqwSCqHr =A/a9 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
