On Wed, Feb 25, 2004 at 10:00:14AM +0100, David Martínez Moreno wrote: > Don't worry :-) > > xlibs now has become a transient package (i.e., a fake package that is > intended to make the transition to the new packages as smooth as possible). Not quite true. It is transitional, but it is not "fake", and it *does* contain important files. > - From the description of xlibs: > > X Window System client libraries metapackage and XKB data > > This package smooths upgrades from Debian 3.0 by depending on the individual > library packages into which each shared object formerly contained in this > package has been split. > > This package is only depended upon by packages that haven't yet been compiled > against the new shared library packages. > > Eventually, if you run deborphan, you should be able to remove xlibs and > whatever other graphical libraries dependencies you have, as the new xlibs > design is far more modular than 4.2.1 one. > > What I mean is that you are seeing only what xlibs contained in 4.2.1 but > only now is splitted in. xlibs will have to live on dpkg is capable of migrating conffiles from one package to another. Some users of earlier experimental 4.3.0 packages saw what happens when the XKB data migrates; they 60 or 70 spurius "changed-conffile" prompts. In my opinion, it is not reasonable by any stretch of the imagination to subject our users to this behavior. When dpkg is fixed, the XKB data can move to xlibs-data, and xlibs-data can Pre-Depend (I think) on dpkg (>= whatever-version-fixed-it). -- G. Branden Robinson | The power of accurate observation Debian GNU/Linux | is frequently called cynicism by branden@debian.org | those who don't have it. http://people.debian.org/~branden/ | -- George Bernard Shaw
Attachment:
signature.asc
Description: Digital signature