lkml.org 
[lkml]   [2004]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [RFC] Splitting kernel headers and deprecating __KERNEL__
Date
On środa 01 grudzień 2004 06:23, Sam Ravnborg wrote:
> > Linked, copied, mount --binded, whatever. Just not under the
> > name /usr/include/user, but something more meaningfull.
>
> Whats wrong with
> /lib/modules/`uname -r`/source/include/user
> /lib/modules/`uname -r`/source/include/$arch

Those are supposed to be userland-only headers that don't just change - they
are gradually expanded. I don't see a point in having `uname -r` in there.

And another thing - distribution vendors will *hate* anyone, that encourages
app developers to add an include path based on which kernel is being
currently run. People, that have their headers tied to their kernels are a
*minority*.

(though iirc eg. netfilter is a mess, so there might be bigger reasons to
ignore my arguments; not that I won't hate you if you do, and I'll have to
patch everything, just to get it compiled)

--
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again
-
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/

\
 
 \ /
  Last update: 2005-03-22 14:08    [W:0.124 / U:0.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site