[sr-dev] Conflict between libcurl4-gnutls-dev and libcurl4-openssl-dev (Debian)

Jan Janak jan at iptel.org
Tue Jun 23 14:24:01 CEST 2009


On 23-06 13:32, Daniel-Constantin Mierla wrote:
>
>
> On 06/23/2009 01:18 PM, Henning Westerholt wrote:
>> On Dienstag, 23. Juni 2009, Iñaki Baz Castillo wrote:
>> > 2009/6/23 Jan Janak <jan at iptel.org>:
>> > > and I have seen more such reports. Openssl received lots of speed
>> > > optimizations over time, unlike gnutls.
>> >
>> > So, is it ok if I change the dependencies in Kamailio to require
>> > libcurl4-openssl-dev instead of libcurl4-gnutls-dev?
>>
>>
>> Hi Iñaki,
>>
>>
>> this would mean that the utils module can't be packaged with  
>> (official) debian anymore, as the licence of openssl don't allow it.  
>> This is basically the same problem as with the tls support, which is  
>> disabled in the debian package as well.
> is it inherited in this case? the tls implementation in core of kamailio  
> is binding directly to openssl library and therefore need for the gpl  
> disclaimer, but in this case utils binds to curl library.
>
> In sip router this is fixed I guess and tls is shipped with debs --  
> anyhow, tls is a module in sr, the core is the same.

If I understand it correctly, we are talking here about Debian control files
that are being kept in the git repository, right? But aren't those files
intended for people who want to build Debian packages themselves, rather than
for official Debian developers? As far as I know official Debian developers
maintain their control files elsewhere, and in fact it is recommended that
upstream projects do not provide their own control files.

If this is the case, does it really matter if we keep libcurl4-openssl-dev in
our control files? We know that all the stuff should work (at least was
developed with) with openssl, so shouldn't this be the default for the people
who attempt to build the packages themselves?

Also note that the -dev packages are only needed to actually build packages,
they are not needed at runtime. They only contain files that are needed to
compile applications that use libcurl. Corresponding runtime libraries are in
libcurl3 (openssl version) and libcurl3-gnutls (gnutls version) and these can
be installed at the same time. What this means is that it is not possible to
*compile* applications for use with libcurl-openssl and libcurl-gnutls at the
same time.

   Jan.



More information about the sr-dev mailing list