From: Christoph Hellwig <hch@infradead.org>
To: Michael Hunold <hunold@convergence.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
J?rn Engel <joern@wohnheim.fh-wedel.de>,
Marcus Metzler <mocm@metzlerbros.de>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Stezenbach <js@convergence.de>
Subject: Re: DVB Include files
Date: Thu, 26 Jun 2003 09:24:44 +0100 [thread overview]
Message-ID: <20030626092444.A26890@infradead.org> (raw)
In-Reply-To: <3EFAAC69.6090709@convergence.de>; from hunold@convergence.de on Thu, Jun 26, 2003 at 10:18:49AM +0200
On Thu, Jun 26, 2003 at 10:18:49AM +0200, Michael Hunold wrote:
> In include/linux/dvb we have the headers that are shared between user
> applications and the kernel driver. As I said above, these are stable and
> never change for the v3 api. In an ideal world, these header files would
> be included in your glibc distribution at /usr/include/linux/dvb
> Currently, you must copy them by hand or create a symlink, because there
> hasn't been an official kernel with the dvb driver subsystem yet.
And that's the whole point. In fact I hear exactly that problem from a
friend at SuSE who maintained an (inofficial?) dvb package. He packaged
the kernel driver but of course it's not part of the official SuSE kernel
and even more so the kernel headers package that is created with the
kernel package but doesn't change during the lifetime of the glibc
package. Now he's not allowed to just write into /usr/include/linux/
either because that directory is owned by the kernel headers package.
Please just get over it and put a copy of the headers into /usr/include/dvb,
this makes life easier for everyone.
next prev parent reply other threads:[~2003-06-26 8:10 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 [this message]
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
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=20030626092444.A26890@infradead.org \
--to=hch@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hunold@convergence.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=js@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mocm@metzlerbros.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