The rest of your mail suggests otherwise
> I don't use RH, and I'm not in a mood to switch to RH just because
> RH has an LK headers maintainer.
It;s not about using RH. At all. You obviously didn't read
my mail. First you say "nobody is doing the work" to which I respond
"I am, and you even don't have to use RH to benifit from it".
> The question is how to make these headers. Who decides what should and
> shouldn't be available to userland?
For the header set I maintain, I did. Based on the criterium "does
this describe a kernel<->userland ABI".
> 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.
You really don't get it.
If a userspace app needs something REALLY special from headers, it
should bloody well come with that header.
> 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.
Ok to take your example: the wireless extension using apps
should include THEIR header for the extensions THEIR released userland
is for, unless they want to use the sanitized headers (which should have
latest). The kernel<->userspace ABI is stable, and compatible between
kernel versions.
> 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
I tried several times to tell you, you just don't want to hear the answer
it seems.
-
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/