On Sat, Apr 22, 2006 at 04:28:53PM +0200, Sam Ravnborg wrote:
> > >...
> >
> > 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.
>
> First off:
> There are many other users that poke direct in the kernel source also.
Kernel space users?
User space users?
Can you give an example of what you are thinking of?
> Secondly and more importantly:
> Introducing kabi/ you will have a half solution where several users will
> have to find their stuff in two places for a longer period.
> kabi/ does not allow you to do it incrementally - it requires you to
> move everything over from a start.
> You may argue that you can just move over a little bit mroe than needed
> but then we ruin the incremental approach.
For kernel space, you can do it incrementally, since the whole kabi/
stuff should be transparent for in-kernel uses.
For user space, you need one switch.
But this switch goes from the current mess with several independent
user space header implementations to one official implementation.
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
