<br><br><div class="gmail_quote">On Tue, Oct 12, 2010 at 4:47 PM, Felipe Crochik <span dir="ltr"><<a href="mailto:felipe@crochik.com">felipe@crochik.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Hi Daniel, </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Almost there…. I don’t get a
compilation error anymore but now my communi package becomes dependent on
libircclient-qt-dev (not libircclient-qt).</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">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. </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">My communi package has:</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Build-Depends: libircclient-qt-dev, …</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">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?</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">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?</span></font><br></p></div></div></blockquote></div><br><br>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 <a href="http://www.tin.org/bin/man.cgi?section=1&topic=dh_install">http://www.tin.org/bin/man.cgi?section=1&topic=dh_install</a> (it even has an example for -dev packages).<br>
<br>Best regards,<br>Attila<br>