Re: release policy changes
Goswin von Brederlow <email@example.com> writes:
> mrvn@frosties:~% apt-cache show mozilla-dev
> Package: mozilla-dev
> Architecture: amd64
> Source: mozilla
> Version: 2:1.7.8-1
> Depends: mozilla-browser (= 2:1.7.8-1), libnspr-dev (= 2:1.7.8-1), libxt-dev, libc6 (>= 2.3.2.ds1-21), libgcc1 (>= 1:3.4.1-3), libglib2.0-0 (>= 2.6.0), libidl0, libstdc++6 (>= 3.4.3-1)
> As you can see clearly from the Depends the package was build against C
> ABI from 1:3.4.1-3 and C++ ABI from 3.4.3-1. All dynamic libraries must
> have those Depends or they already violate policy. And that version maps
> to an uniqe ABI.
I think you're confusing the C++ ABI with the SONAME of libstdc++.
They're not necessarily the same thing, although right now they tend to
change at the same time. Having the SONAME of libstdc++ change is
actually probably more likely to cause problems than a C++ ABI change
(since the latter is likely to be an edge case at this point), but either
can cause problems.
I'm not sure why it would be useful to express the C++ ABI as a
dependency, but if that's what one wants to do, I think the original
poster is right and it's not currently happening.
> Further doesn't the package name for libgcc1 and libstdc++ always change
> with abi changes? E.g. libstdc++5 vs. libstdc++6.
The libgcc SONAME isn't really the same as the C ABI either, but the C ABI
realistically changes so rarely that I don't think it's worth worrying
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>