Max Kellermann (Sat, 21 Mar 2009 09:37:03 +0100):
> On 2009/03/21 08:57, Sebastian Dröge <sl...@circular-chaos.org> wrote:
> > libmpc will be uploaded to unstable in the next days. Please port your
> > package to the new API ASAP, it will most probably fail to build after
> > the upload to unstable.
> I do not understand the hurry. Do you plan to remove the old libmpc
> package? The Debian shared library policy guarantees that older
> package continue to work/build (with older SO versions) even when a
> new API of a library gets uploaded. Please explain how this bug
> report relates to the Debian shared library policy.
New major versions of a library can be uploaded in two ways: in a way
that recompilation against the old version is allowed (by keeping the
old -dev package around), or by forcing recompilation against the new
version. This second way is preferred, but if there have been API
changes, work is needed to port the application to the new API. I’m
working with Sebastian Dröge to see if this libmpcdec transition can be
done “the second way”, and for that we need to start seeing applications
ported to the new API.
Hope this clears up things for you, please let me know if that’s not the
case. The important thing is that this is about the development packages,
and not about the shared libraries (libmpcdec3 and libmpcdec6 are
co-installable).
Cheers,
--
- Are you sure we're good?
- Always.
-- Rory and Lorelai
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
