> A company COMP wishes to use LIB in its products in a statically linked
> manner
> and asserts that this is not possible with LGPL code.
Their assertion is incorrect. The LGPL does not "know" of any difference
between static linking and dynamic linking. In either method, the code "mixes"
on the binary level.
> distribute the LGPL'd portion as a dynamically linked library
> which the end user could replace if desired or a API-based rebuild system.
> This may
> apparently have undesirable commercial consequences for COMP.
The only requirement of the LGPL is that COMP must distribute the code for LIB,
or optionally whatever portion of LIB they actually use. For exempt, if they
only use PMRCODE, then they only need to make that available *upon request*.
Now some companies (e.g., RedHat) make all their GPL and LGPL code available.
But technically, COMP only needs to respond to e-mail or written requests.
Also, if COMP makes code changes to LIB or PMRCODE or whatever, they must make
these available to the community.
The main difference between the LGPL and BSD licenses is that the LGPL requires
COMP to make the code and any modifications available upon request to the
community. The BSD allows Microsoft to take the TCP/IP stack and not distribute
any changes they make.
I don't have a chance right now, but the FSF has a nice FAQ about their
different licenses, and I'm sure this is one of the common cases addressed.
Best regards,
-Geoff
P.S. While I'm considering making my code available under the BSD license, I
generally *like* the LGPL because it requires changes go back to the community.
I'm just getting tired of explaining licenses. IANAL.
---
Prof. Geoffrey Hutchison
Assistant Professor, Department of Chemistry
University of Pittsburgh
http://hutchison.chem.pitt.edu/
Office: (412) 648-0492
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Blueobelisk-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/blueobelisk-discuss
