I didn't miss the point. I don't use RH, and I'm not in a mood to
switch to RH just because RH has an LK headers maintainer.
The question is how to make these headers. Who decides what should and
shouldn't be available to userland? What of the myriad of tools which
make modules, or use deep kernel headers? What of the packages that try
hard to keep subset headers synchronized but get frustrated because
update patches get dropped? What am I supposed to do when I want to use
several of these packages and their updates conflict with each other?
AFAIK, you don't have a package that contains all the -current- headers
for all the current versions of all these various projects applied to
the kernel headers and then sanitized. I want to use my hardware that
is supported by version X of the package's software but the headers only
have version M supported. Wireless extensions for example.
With everybody maintaining separate headers things get messy.
The question is how to make these headers. Nobody wants to say how and
when someone needs an answer, even a distro maintainer, the answer is a
flippant "don't use kernel headers / use your vendor". I haven't seen
otherwise and believe me, I would latch on to the answer because I'm
always having to tailer headers to make things work for a variety of
distributions.
David
Arjan van de Ven wrote:
>On Mon, 2003-05-19 at 19:59, David Ford wrote:
>
>
>
>>Someone please step up to the plate and explain how to convert kernel
>>headers into sanitized headers for /usr/include.
>>
>>
>
>It seems you totally miseed the entire point.
>It shouldn't be an automatic conversion. It should be a well thought
>subset cleaned from kernel private stuff.
>
>I maintain such a subset for my employer and it's free for all to use
>(it's GPL after all).
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri May 23 2003 - 22:00:35 EST