Re: Proposal to improve package configuration upgrades
Jonas Smedegaard <firstname.lastname@example.org> writes:
> Do Config::Model support migration from one model to another?
Yes. In fact model version n can include specific attribute to deal
with migration from n-1 to n.
> Example: CUPS 2.x has boolean option foo, which is changed in CUPS 3.x
> to numeric option foobar.
In such a case, CUPS3.x model would need to speficy that:
- boolean option foo is status deprecated (which means the value can
be managed, but the option foo is hidden from the user in the
- the default value of foobar can be computed from foo value (using
compute attribute of Value object. See  for gory details)
More complex value migration scenarios are possible.
All the best
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner
domidumont at irc.freenode.net
ddumont at irc.debian.org