Re: [PATCH] 'make headers_install' kbuild target.

[Adrian Bunk <bunk@stusta.de>]

On Sat, Apr 22, 2006 at 04:14:10PM +0200, Sam Ravnborg wrote:
> On Sat, Apr 22, 2006 at 01:03:03PM +0100, David Woodhouse wrote:
> > On Sat, 2006-04-22 at 11:33 +0200, Adrian Bunk wrote:
> > > My thirst thought is:
> > > Is this really the best approach, or could this be done better?
> > 
> > I think it's the best way to start, although I agree with you entirely
> > about what we should strive for in the end.
> > 
> > > I'm currently more a fan of a separate kabi/ subdir with headers used by 
> > > both headers under linux/ and userspace.
> > 
> > I agree -- I'd like to see that too. But Linus doesn't like that
> > approach very much.
> Thats bacause the kabi subdir is broken by design.
> Any approach that does not take into account the existing userbase is
> broken by design and should be avoided.
> The only sensible solution is to move out the kernel internal headers
> from include/* to somewhere else.
> And then slowly but steady let include/linux and include/asm-* be the
> KABI.
>...

What exactly is the problem with creating the userspace ABI in 
include/kabi/ and letting distributions do an
  cd /usr/include && ln -s kabi/* .
?

Or with creating the userspace ABI in include/kabi/ and letting 
distributions install the subdirs of include/kabi/ directly under 
/usr/include?

These are two doable approaches with a new kabi/ that avoid needless 
breaking of userspace.

> 	Sam

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed