Bug#697697: ecere-sdk: binary package conflict with eclib

[Jerome St-Louis]

Thanks Dmitrijs.

I already have /usr/lib/i386-linux-gnu/ec/libec.so

I will verify, but I think the symlink /usr/lib/i386-linux-gnu/libec.so
might not be required

I think those symlinks are only required for libecere and libecereCOM since
they are linked by the system dynamic linker...
The /ec/ path are searched by the eC dynamic linker for imported modules,
which "ec" is.

But I'll have to test and verify to make sure everything still works fine.

Regards,

Jerome


On Wed, Jan 9, 2013 at 4:54 AM, Dmitrijs Ledkovs <xnox at debian.org> wrote:

> On 9 January 2013 00:01, Jerome St-Louis <jerstlouis at gmail.com> wrote:
> > Will renaming the package mean renaming the actual library as well for
> > Lintian to be happy?
> >
> > The ecere-dev package also provides /usr/lib/i386-linux-gnu/libec.so
> >
>
> Renaming just the package will not be enough as there would still be
> left file conflict with the other libec.
> So you'd need to rename package, rename library or use a different
> path (e.g. /usr/lib/i386-linux-gnu/ec/libec.so or
> /usr/lib/i386-linux-gnu/ecere/libec.so).
> (This can be just a Debian patch & not upstream)
> And we can silence lintian's chatter about package name not matching the
> soname.
>
> Regards,
>
> Dmitrijs.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20130110/1d4c92da/attachment.html>