Re: build depends on kernel-headers
>>"Aaron" == Aaron Lehmann <firstname.lastname@example.org> writes:
Aaron> So you're saying it's better to hardcode syscall numbers and stuff
Aaron> than using the kernel headers? Suuuure...
We already have a process for packages that actually do need
kernel headers, and are thus dependent on particular kernel
versions. Are you also sure you have considered the impact of using
one set of kernel structures, and linking with a libc that uses
perhaps an incompatible set of kernel-structures?
Kernel modules are loaded into the kernel, and thus are in the
kernel's context, but user space modules, linked with libc, are
playing with fire when they assume that the incompatible kernel
structures they have been compiled with are not going to cause
If your package does meet the criteria, it is extremely rare,
and I do not think it is wirth the infrastructure to cater to the
very few packages that shall meet these criteria.
Under deadline pressure for the next week. If you want something, it
can wait. Unless it's blind screaming paroxysmally hedonistic...
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C