libnl3 soname change
last week I did an upload of the current version 3.2.3 libnl3 to experimental.
Libnl >= 3.2 is for example necessary for network-manager.
Beginning from 3.2 upstream changed the soname changed from libnl3 to
libnl3-200 and due to now correct .pc files it was possible to also create
separate packages for the individual libraries instead of cramming all of them
into one package.
So the question would be on how to proceed to get this into unstable without
breaking to much.
Another question for the installer folks: should the udeb stay as it is, or
should it be split too.