Bug#361872: debconf-copydb: Trashes debconf database in /target
On Mon, Jun 19, 2006 at 01:23:17PM -0400, Joey Hess wrote:
>> What do you propose in this case -- hacking support for this kind of
>> "undefined encoding" stuff into cdebconf?
> No, I don't think that cdebconf should worry about supporting this stuff
> beyond not corrupting it if reading a debconf database file.
Well, debconf-copydb does:
- Read in first and second config.dat.
- Read in first and second template.dat.
- Make a new second config.dat, writing all the data from RAM.
- Make a new second template.dat, writing all the data from RAM.
All this is done via the normal reading functions, which parses everything
over to cdebconf's internal C structs (AFAICS). How should cdebconf keep
track of all this information (which I guess is what you mean by "not
corrupting") without adding almost full support for it (modulo charset
conversion) everywhere? This looks like a quite extensive change to me.
/* Steinar */
--
Homepage: http://www.sesse.net/
Reply to: