iLBC license issue

Daniel Pocock daniel at readytechnology.co.uk
Sun Mar 19 20:28:04 UTC 2006


>Under the conditions you described, I'd think it is non-distributable
>if it links to iLBC. iBLC would have to be _removed_.
>
>  
>
>>>http://www.ilbcfreeware.org/documentation/gips_iLBClicense.pdf
>>>      
>>>
>
>  
>
>>Can iLBC be split into a separate package?
>>    
>>
>
>That wouldn't help for GPLed apps. They cannot link to
>GPL-incompatible libs.
>
>  
>
Yes, that is understood.

But can this be done in reverse - i.e:

- kphone and other apps adopt/use an API for dynamically linking codecs

- The API (and supporting libs) are licensed under Vocal or similar 
terms, so the GPL applications can use this library/API

- if someone wants to independently distribute non-GPL codecs, they only 
have to observe the Vocal license conditions and conform to the API

I don't believe this approach goes against the spirit of the GPL, 
although if anyone feels that is the case then please feel free to 
comment on it.




More information about the Pkg-voip-maintainers mailing list