libnl vs. libnl2 madness

[Stefan Schmidt <stefan@datenfreihafen.org>]

Hello.

The last hours I was trying to compile wpa_supplicant with nl80211 support. That
needs netlink support through libnl or libnl2.

Enabling the option to use libnl2, not that easy to find, still breaks with
missing header files. Checking the libnl2 source shows that they are provided.
After some head on the table banging I found:

commit 880e00d3b7ccf66d9421a06bc28e553e07842b59
Author: Michael 'Mickey' Lauer <mickey@vanille-media.de>
Date:   Tue Nov 24 16:33:06 2009 +0000

    libnl2: change includedir to not step over libnl1; also convert to new staging

which brings in this:

+includedir = ${prefix}/include/libnl2

Resulting in header files getting staged in to libnl2/netlink/fooo instead of
netlink/foo.

This obviously breaks every application that uses libnl2. Reverting this part
makes wpa_supplicant happy.

Can somebody bring some light into this? Do we have libnl1 only recipes in our
metadata?

If libnl2 overrides header files from libnl with other content this is of course
bad. As is to move away header files from the usual location and breaking apps.

regards
Stefan Schmidt