From: Jaroslav Kysela <perex@perex.cz>
To: Jordi Mallach <jordi@debian.org>, alsa-devel@alsa-project.org
Cc: pkg-alsa-maintainers@lists.alioth.debian.org
Subject: Re: [alsa-devel] ABI breakage in alsa-lib 1.2
Date: Wed, 15 Jan 2020 09:47:12 +0100 [thread overview]
Message-ID: <a009ee4f-e0c5-a944-6575-b0df79388fb6@perex.cz> (raw)
In-Reply-To: <1fbf9bffb1f13e1ea8e1212a633998b9e6380298.camel@debian.org>
Dne 10. 01. 20 v 23:58 Jordi Mallach napsal(a):
> [Please Cc me on replies, I'm not currently subscribed to alsa-devel]
>
> Hello,
>
> I'm one of the ALSA Debian maintainers, and some weeks ago I looked
> into updating our ALSA packages to 1.2.1.
>
> I quickly noticed there's been some fundamental change to libasound2,
> one that appears to break ABI and should have warranted an soname bump
> at least.
>
> With the split of the snd_tplg API to the new libatopology2, libasound2
> has been left missing that part of the API that was part of the
> asound.h header, etc. This could have been a somewhat lesser issue if
> libasound2 linked to libatopology, but unfortunately this goes in the
> other direction, so the ABI and API breakage is not avoided.
>
> I cannot update alsa-lib in this state. I could hack around and patch
> it to reinstate the missing api in libasound, but this sounds like pain
> and suffering for everyone involved. How should we move forward with
> this?
>
> I am sorry I only come up with this 2 months after the release when I
> had identified the problem many weeks ago, I've been extremely busy.
It's not a problem at all. Those API/ABI is used only in the alsatplg utility
from the alsa-utils package which has the specific usage - compilation the
topology files from the configuration file to the binary form for the driver.
This tool is used only by the developers. I believe that you have zero users
for this. No other applications are expected to be touched. I would not do
this split, if it affects something serious.
Jaroslav
>
> Thanks,
> Jordi
>
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2020-01-15 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 22:58 [alsa-devel] ABI breakage in alsa-lib 1.2 Jordi Mallach
2020-01-15 8:47 ` Jaroslav Kysela [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=a009ee4f-e0c5-a944-6575-b0df79388fb6@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=jordi@debian.org \
--cc=pkg-alsa-maintainers@lists.alioth.debian.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;
as well as URLs for NNTP newsgroup(s).