the linuxwacom ebuild should use the headers from the current kernel, because otherwise it might not use the correct API when for example the glibc was compiled against 2.4 headers while you are running a 2.6 header Reproducible: Always Steps to Reproduce: 1. 2. 3.
Can you give an example of where this actually breaks something that linuxwacom uses, rather than something theoretical and lacking evidence?
I'm not so sure this is actually a problem. Aren't there quite a few other programs that would fall into the same category?
hey hey... no need to get angry. in src/wacusb.c:USBParseData /* dispatch event */ switch (pEv->type) { #ifdef EV_SYN case EV_SYN: /* kernel 2.6 */ #endif case EV_MSC: /* kernel 2.4 */ ... $ grep EV_SYN /usr/include/linux/input.h $ grep EV_SYN /usr/src/linux/include/linux/input.h #define EV_SYN 0x00 $ if linuxwacom is compiled against 2.4 headers, the USB driver cannot correctly parse the data anymore, because it will just ignore some input events. This results in the tablet just not working. When you run wacdump, you will get an endless list of 'Invalid arguments'. evidence enough?
I think the proper solution would be to force >=linux-headers-2.6 if USE=usb.
Fixed in 0.6.7
