public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: mocm@mocm.de, Michael Hunold <hunold@convergence.de>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: DVB Include files
Date: Wed, 25 Jun 2003 18:49:11 +0100	[thread overview]
Message-ID: <20030625184911.B29537@infradead.org> (raw)
In-Reply-To: <20030625172703.GC1770@wohnheim.fh-wedel.de>; from joern@wohnheim.fh-wedel.de on Wed, Jun 25, 2003 at 07:27:03PM +0200

On Wed, Jun 25, 2003 at 07:27:03PM +0200, Jörn Engel wrote:
> Christoph, while I agree with you, I also see why a lot of people just
> symlink /usr/include/linux to /usr/src/.../include/linux.  Pure
> convenience and the lack of a dedicated collection of userspace
> headers outside a distributions scope.

Well, that symlinking is okay as long as you never ever touch /usr/src/linux
again.

> Or did I miss something important and just exposed my stupidity?

No one said they can't be the same header and actually maintaining
them in the kernel tree is fine to.  Just put them in a different
location for userspace so you can update them independant of the
kernel.  Look at e.g. XFS - most headers in /usr/include/xfs/ are
just copied from fs/xfs/ in the kernel tree.  But they're always
the ones matching the libxfs you installed no matter what XFS
version your currently running kernel has (or no XFS at all).

And that's the fundamental issue here, the userland header must
be independant from the actually running kernel or some random
source tree that's somewhere on your disk.  Copying the content
to /usr/include/linux does work but it's really suboptimal.  You
don't want to upgrade your libc just because you want to be able
to use the new features in the dvb driver you just installed.
A separate dvb-dev packages that has a copy of those headers
in /usr/include/dvb is the much better choice.


      reply	other threads:[~2003-06-25 17:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 15:06 DVB Include files Sam Ravnborg
2003-06-25 15:08 ` Christoph Hellwig
2003-06-25 15:42   ` Sam Ravnborg
2003-06-25 16:17     ` Michael Hunold
2003-06-25 16:49       ` Marcus Metzler
2003-06-25 16:55         ` Christoph Hellwig
2003-06-25 17:13           ` Marcus Metzler
2003-06-25 17:16             ` Christoph Hellwig
2003-06-25 17:22               ` Marcus Metzler
2003-06-25 17:24                 ` Christoph Hellwig
2003-06-25 17:30                   ` Marcus Metzler
2003-06-25 17:50                     ` Christoph Hellwig
2003-06-25 18:09                       ` Marcus Metzler
2003-06-25 18:15                         ` Christoph Hellwig
2003-06-25 18:43                           ` Marcus Metzler
2003-06-25 19:42                             ` Jörn Engel
2003-06-25 20:09                               ` Marcus Metzler
2003-06-25 20:23                                 ` Jörn Engel
2003-06-25 20:48                                   ` Marcus Metzler
2003-06-25 21:03                                     ` Christoph Hellwig
2003-06-25 21:38                                       ` Marcus Metzler
2003-06-26 13:54                                         ` Henning P. Schmiedehausen
2003-06-25 23:08                                   ` Alan Cox
2003-06-26  8:18                                     ` Michael Hunold
2003-06-26  8:24                                       ` Christoph Hellwig
2003-06-26 13:20                                         ` Johannes Stezenbach
2003-06-25 21:03                             ` Christoph Hellwig
2003-06-25 17:27           ` Jörn Engel
2003-06-25 17:49             ` Christoph Hellwig [this message]

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=20030625184911.B29537@infradead.org \
    --to=hch@infradead.org \
    --cc=hunold@convergence.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mocm@mocm.de \
    --cc=sam@ravnborg.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