[poky] /usr/include/libnl3 or /usr/include

[Jean-Francois Dagenais]

Hi guys,

There's been a couple of time when I've hit snags where packages use their version numbers in the paths of stuff they provide. This poses a small challenge where dependent recipes might have to specifically account for this "special" path.

For example, libnl is using /usr/include/libnl3 and wpa_supplicant has to specifically "hack" its configure process to be able to find the libnl headers.

Since libnl does explicitly that it cannot co-exist with it's previous versions:
RREPLACES_${PN} = "libnl2"
RCONFLICTS_${PN} = "libnl2"

what is the point of the sub-path?

Would you receive a patchset which moves libnl's headers files back at /usr/include (or rather: ${includedir}) ?

I suspect this would also set a precedent.