On Tue, 2011-11-08 at 13:05 -0500, Bill Nottingham wrote: > Dan Williams (dcbw@xxxxxxxxxx) said: > > I believe libnl3 *might* be parallel installable; I've had conversations > > with tgraf about how to make it so. I'll investigate once the upstream > > git repo comes back online. In the past the problem was mainly with the > > devel package and the location of the headers and the .pc file (ie, it > > was always /usr/include/netlink no matter what the version of libnl) but > > I believe Thomas fixed that earlier this summer for libnl3. > > I'm less concerned about the old version being around to develop against - > I'd just rather not have the whole repo hae issues while people are still > porting. It certainly has a different soname, so yeah, we can have a -compat package. But that would still mean a ton of stuff busted for rebuilds while packages get fixed up. A few upstream packages already work with libnl2, and the delta between 2 and 3 is hugely smaller than from 1 to 3. repoquery --whatrequires libnl for F16 says: NetworkManager (fixed upstream) anaconda crda (wifi regulatory database) dropwatch hostapd (upstream works with libnl2) ipvsadm iw (upstream works with libnl2) keepalived kismet knemo libvirt lldpad netcf netlabel_tools powertop python-ethtool quota-nld sssd wimax wimax-tools wpa_supplicant (upstream works with libnl2) Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
