[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What to do?

On Tue, Jan 25, 2011 at 11:43 AM, Michael <m.b3941@web.de> wrote:
> Hi again,
> Hope this is a more intelligent question than the last one ;-)
> I want to get rid of
> W: libsnacc0c2: package-name-doesnt-match-sonames libasn1c++0
> libasn1cCebuf0 libasn1cebuf0 libasn1cmbuf0 libasn1csbuf0 libasn1ctbl0
> I didn't do the naming, but it's true, what lintian is saying.
> I don't really want to rename neither the (binary) lib-package nor the
> libraries, for that would force every user of libsnacc to change their
> packages too. I think I can add extra (sym)links to "/usr/lib" starting
> with libsnacc0c2 pointing to the (real) libraries. I haven't checked, if
> that will help and/or work. Simplest way would be to override, but I do
> not like that, unless there is absolutely no other way.
> So the question is : What is the usual way?
> Or, if there is no general solution : What is the suggested way?

I think the best thing to do is fix such a problem the "right way"
post-squeeze-release [1]. That means renaming the library binary
packages correctly so that each library package contains only one
binary library file, and have one -dev package that depends on all the
library packages. You would then have to request rebuilds on all
depending packages so that they properly depend on your new names. If
you are concerned about users having to change their packages, you can
create a transitional package which, for now, depends on all the
individual libraries. In the future, users that build packages using
your -dev will only depend on the libraries that they actually
need/use. That is the general solution.

[1] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html


Reply to: