On Wed, Mar 23, 2011 at 22:59:22 (CET), Alessandro Ghedini wrote:
> On Wed, Mar 23, 2011 at 10:24:22PM +0100, Reinhard Tartler wrote:
>> On Wed, Mar 23, 2011 at 21:55:14 (CET), ghedo-gu...@users.alioth.debian.org
>> > The following commit has been merged in the master branch:
>> > commit c13b7176fe7823bead9078961696295f94ff26e7
>> > Author: Alessandro Ghedini <al3x...@gmail.com>
>> > Date: Wed Mar 23 20:55:45 2011 +0100
>> > update *.symbols files for the libraries
>> > diff --git a/debian/libecasound22.symbols b/debian/libecasound22.symbols
>> > index d7af24a..5605429 100644
>> > --- a/debian/libecasound22.symbols
>> > +++ b/debian/libecasound22.symbols
>> > @@ -65,6 +65,7 @@ libecasound.so.22 libecasound22 #MINVER#
>> > _ZN10ECA_LOGGER8lock_repE@Base 2.7.2
>> > _ZN10ECA_OBJECTD0Ev@Base 2.7.2
>> > _ZN10ECA_OBJECTD1Ev@Base 2.7.2
>> > + _ZN10ECA_OBJECTD2Ev@Base 2.7.2
>> Can you actually read this mangled mess of symbols?
>> I still think .symbols file are largely practically useless for C++
> AFAIK they are not meant to be read by humans, but they can be used by dpkg
> for generating more accurate library dependencies.
They are supposed to be actively maintained by the package maintainer,
so no, AFAIUI they are supposed to be read by humans.
> Anyway, they can be demangled using c++filt(1), if needed.
And I'd say this is badly needed in this case at hand.
> Also, there is the no-symbols-control-file lintian tag. It's just whishlist
> severity, but IMHO it's nice to keep lintian as silent as possible :)
We had this argument before. We are not linitan pleasers, we want to
please our users by creating technically correct and maintainable
packages. Not every lintian warning makes sense, please take them with a
grain of salt.
Reinhard Tartler, KeyID 945348A4
pkg-multimedia-maintainers mailing list