[maemo-developers] Packaging - dpkg-shlibdeps problem

[From: Attila Csipa]

On Tue, Oct 12, 2010 at 4:47 PM, Felipe Crochik <felipe at crochik.com> wrote:

>  Hi Daniel,
>
> Almost there…. I don’t get a compilation error anymore but now my communi
> package becomes dependent on libircclient-qt-dev (not libircclient-qt).
>
>
>
> Maybe I got it the “lib” idea wrong: libircclient-qt and
> libircclient-qt-dev share the exact same code the only difference is on the
> Makefile (and control). The dev package installs “everything” (headers, lib,
> mkspecs) and the “release” package just the lib.
>
>
>
> My communi package has:
>
> Build-Depends: libircclient-qt-dev, …
>
>
>
> Now when I create the communi package using dh_shlibdeps it adds the
> dependency to the “libircclient-qt-dev”. I assume there is a way to tell the
> libirccclient-qt-dev package that it’s “runtime” version is
> “libircclient-qt” or something like that, can you help me again?
>
>
>
> Once you are “here” anyway: I would assume there is a way to have both
> libircclient-qt and libircclient-qt-dev not need each to have its own
> “source” code. Is there a “smarter/better/easier” way of creating lib
> packages?
>


You answered your question right there - you can (and should) generate all
debs from one source package - debhelper's dh_install helps you control
which file goes into which package via .install files. See
http://www.tin.org/bin/man.cgi?section=1&topic=dh_install (it even has an
example for -dev packages).

Best regards,
Attila
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20101012/15679f66/attachment.htm>