-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Feb 25, 2009 at 09:28:52AM +0100, Dominique Dumont wrote:
>Of course, there's no miracle. For the merge to work automatically and >the result to be valid, the semantic of the configuration file must be >known by Config::Model. This is done by describing the structure and >constraints of the configuration file in a model (hence the >Config::Model name). Do Config::Model support migration from one model to another? Example: CUPS 2.x has boolean option foo, which is changed in CUPS 3.x to numeric option foobar. - Jonas P.S. Please cc me on responses, I am not subscribed to -devel - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmlHtcACgkQn7DbMsAkQLjcSACfSHHm6+wMFVanffFsDWr9brsl 1gkAoJRQWvyvmGEuRxA7aC3iqhkHfIsc =V7EK -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
