<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Console'; font-size:9pt; font-weight:400; font-style:normal;">On Dienstag, 23. Juni 2009, you wrote:<br>
> > is it inherited in this case? the tls implementation in core of kamailio<br>
> > is binding directly to openssl library and therefore need for the gpl<br>
> > disclaimer, but in this case utils binds to curl library.<br>
> ><br>
> > In sip router this is fixed I guess and tls is shipped with debs --<br>
> > anyhow, tls is a module in sr, the core is the same.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Hi Jan,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> If I understand it correctly, we are talking here about Debian control<br>
> files that are being kept in the git repository, right? But aren't those<br>
> files intended for people who want to build Debian packages themselves,<br>
> rather than for official Debian developers? As far as I know official<br>
> Debian developers maintain their control files elsewhere, and in fact it is<br>
> recommended that upstream projects do not provide their own control files.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>sure, our debian control files are different then the official ones. And they <br>
are maintained in a different repository, e.g. in "pkg-voip" for kamailio. But <br>
they are synchronised from time to time.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> If this is the case, does it really matter if we keep libcurl4-openssl-dev<br>
> in our control files? We know that all the stuff should work (at least was<br>
> developed with) with openssl, so shouldn't this be the default for the<br>
> people who attempt to build the packages themselves?<br>
><br>
> Also note that the -dev packages are only needed to actually build<br>
> packages, they are not needed at runtime. They only contain files that are<br>
> needed to compile applications that use libcurl. Corresponding runtime<br>
> libraries are in libcurl3 (openssl version) and libcurl3-gnutls (gnutls<br>
> version) and these can be installed at the same time. What this means is<br>
> that it is not possible to *compile* applications for use with<br>
> libcurl-openssl and libcurl-gnutls at the same time.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I've nothing against it, just wanted to note that it makes packaging a bit <br>
harder from a debian POV.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Henning<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>