mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 'make headers_install' kbuild target.
Date: Sat, 22 Apr 2006 16:28:53 +0200	[thread overview]
Message-ID: <20060422142853.GB25926@mars.ravnborg.org> (raw)
In-Reply-To: <20060422142043.GD5010@stusta.de>

> >...
> 
> 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.

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.

	Sam

  reply	other threads:[~2006-04-22 19:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22  2:17 David Woodhouse
2006-04-22  9:33 ` Adrian Bunk
2006-04-22 12:03   ` David Woodhouse
2006-04-22 12:38     ` Adrian Bunk
2006-04-22 12:48       ` David Woodhouse
2006-04-22 13:20         ` Adrian Bunk
2006-04-22 13:36           ` David Woodhouse
2006-04-22 14:11             ` Adrian Bunk
2006-04-22 14:26               ` David Woodhouse
2006-04-22 14:44                 ` Adrian Bunk
2006-04-22 14:56                   ` David Woodhouse
2006-04-22 15:30           ` David Woodhouse
2006-04-22 21:13             ` Arnd Bergmann
2006-04-23  7:09               ` Arjan van de Ven
2006-04-23 16:51                 ` Arnd Bergmann
2006-04-23 17:00                 ` Joshua Hudson
2006-04-22 14:14     ` Sam Ravnborg
2006-04-22 14:20       ` Adrian Bunk
2006-04-22 14:28         ` Sam Ravnborg [this message]
2006-04-22 14:47           ` David Woodhouse
2006-04-22 14:50           ` Adrian Bunk
2006-04-28 18:15             ` Rob Landley
2006-04-28 18:27               ` David Woodhouse
2006-04-28 19:59                 ` Rob Landley
2006-04-22 14:35         ` David Woodhouse
2006-04-23 20:47 ` David Woodhouse
2006-04-24  0:12 ` David Woodhouse
2006-04-28 18:13 ` Rob Landley
2006-04-28 18:22   ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060422142853.GB25926@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®