On 3/6/06, Olivier Galibert <[email protected]> wrote:
> On Mon, Mar 06, 2006 at 08:52:48AM +0100, Arjan van de Ven wrote:
> > On Mon, 2006-03-06 at 02:17 +0100, Olivier Galibert wrote:
> > > I'm looking at the changes in the asound.h file, and especially at
> > > commit 512bbd6a85230f16389f0dd51925472e72fc8a91, and I've been
> > > wondering if it's acceptable compatibility-wise. All the structures
> > > passed through ioctl (and ALSA is 100% ioctl) have been renamed from
> > > sndrv_* to snd_*. That breaks source compatibility but not binary
> > > compatibility.
> >
> > only if you are "stupid" enough to use kernel headers in your userspace!
> > Which you shouldn't do normally
>
> Does that mean it is the responsability of whoever packages the
> headers for userspace consumption to rename the structs back? Or that
> every application should come with its own copy of the kernel headers
> it may need and be ready for massive source-level breakage when
> rebasing?
>
> I'm just trying to understand if we care about source compatibility
> for userspace or not.
>
Userspace apps should not include kernel headers, period.
So, userspace applications really shouldn't care.
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
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]
