Re: [Opensync-users] Support for bluetooth transport over SyncML ?

[Armin B. <arm...@de...>]

Ademar de Souza Reis Jr. wrote:
> Armin Bauer wrote:
> 
>>Ademar de Souza Reis Jr. wrote:
>>
>>>Please remember that BlueZ is GPL, so libsyncml must also be released
>>>under this license. Making bluetooth support optional is also a
>>>possibility.
>>>
>>
>>Why? libsyncml is LGPL which is compatible to the GPL so the license is
>>fine. The only implication of this is that if you want bluetooth
>>support, you would not be able to use libsyncml with a propietary
>>program (since this would also link against bluez).
>>
> 
> 
> LGPL is compatible with GPL, but not the other way around. What I
> mean by "must also be released under this license" is that if
> you link to BlueZ, you can't use libsyncml as LGPL anymore, so
> either* you also release it under GPL or make bluez linkage
> optional at compilation time.

ok. so we mean the same thing. yes, bluez linkage is of course going to
be optional.

> 
> Of course, the code can still be LGPL so that someone can
> recompile it manually without linking to bluez, but since
> libsyncml will be redistributed (by linux distros, for
> example) and considered a standard library, I believe
> it's a good idea to have the licensing terms clearly
> defined.
> 
> * possibilities such as releasing BlueZ under LGPL, etc
> not cosidered for simplicity :-)
> 
> Cheers,
>   - Ademar
>