[Pkg-kbd-devel] Bug#734164: console-data: should conflict with console-setup

[Anton Zinoviev]

Sorry for the late responce.

On Tue, Feb 11, 2014 at 10:07:26PM +0100, Michael Schutte wrote:
> 
> I see, thanks for elaborating.  This does sound appealing, but what
> should happen in an upgrade if the package into which we move the
> conffiles (IMHO this should be console-setup) is not installed on a
> particular system?  Unless we add dependencies from console-common and
> kbd (this one would be circular) to console-setup,

If this package is console-setup, then we can do the following: we move 
the few important scripts from console-common to console-setup, then we 
remove console-common from the archive and make console-setup to provide 
and replace console-common.  As Christian has notices, this will ensure 
that console-setup gets installed on upgrade.

> What do you think of the plan that I've already hinted at: Drop
> everything in /etc from the console-common and kbd binary packages.
> dpkg will of course leave them behind on upgrade, and they are only
> actively removed through maintainer scripts if they are all unmodified.
> Systems which have been relying on the legacy features of kbd and
> console-common can thereby continue to do so, whereas new installs are
> unencumbered by the historical clutter.

I don't feel myself competent to give a good answer. I suppose your 
method can work but I think other people who know better than me how 
exactly the Debian system works (as a whole) should be able to give a 
better answer.

Anton Zinoviev