On Mon, Dec 06, 2010 at 01:50:17PM +0100, Julien Cristau wrote: > On Sun, Dec 5, 2010 at 20:17:32 +0100, Michael Schutte wrote: > > I’m not at all comfortable with switching from console-tools to kbd > > right now, though. It feels like a bad idea to change the default from > > a package which is installed nearly everywhere to the 13%-popcon kbd, in > > the middle of a freeze. I’m really annoyed at myself for not pushing > > this long-needed transition right after the release of Lenny, as I had > > originally planned. > > > As long as console-tools recommends console-data and console-common that > doesn't seem workable. Or can we switch those to console-setup | > console-data, console-setup | console-common?
I believe we can. Just like kbd’s, console-tools’s primary purpose is
to provide utilities, so it doesn’t really require data files anyway.
So, if I’m not missing anything,
console-tools:
Recommends: console-setup | console-data, console-setup | console-common
kbd:
Depends: console-setup | console-common
Recommends: console-setup | console-data
seems like the smallest fix to do the job. The splashy and
brdesktop-common package also pull in console-common and console-data,
respectively, but I suppose we can ignore this for now.
Is there something I don’t know about console-common? It should be
completely superseded by console-setup, and a quick look at the package
appears to prove this (the init script quits right away if setupcon is
present, which makes the install-keymap binary irrelevant, and
kbd-config is just a wrapper).
All the best,
--
Michael Schutte | mi...@{uiae.at,debian.org}
Innsbruck, Austria | happily accepting encrypted mail
OpenPGP: 0x16fb 517b a866 c3f6 8f11 1485 f3e4 122f 1D8C 261A
signature.asc
Description: Digital signature
