[Python-3000] C API for ints and strings (original) (raw)
Nicholas Bastin nick.bastin at gmail.com
Sun Sep 9 11:06:37 CEST 2007
- Previous message: [Python-3000] C API for ints and strings
- Next message: [Python-3000] C API for ints and strings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/9/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> The LGPL has no requirement that you convey source for unmodified > libraries. Linkage does not imply modification.
Why do you say that? LGPL 2.1, section 6a) (talking about "work that uses the Library"): a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) So you must "accompany the work with complete source code for the Library".
You're being awfully selective in your reading. Section 6a is immediately preceded by a statement which says:
"Also, you must do one of these things:"
6a is but one of 5 choices.
Those choices are:
"b) Use a suitable shared library mechanism for linking with the Library." "c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution." "d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place." "e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy."
Pick any one of those options you like that doesn't involve shipping source code. Using standard shared libraries is a "suitable shared library mechanism".
Also, the LGPLv3 in section 4d.1 specifies the same "Use a suitable shared library mechanism for linking with the Library." This is more relevant, since GMP is licensed under v3 and not v2.1.
-- Nick
- Previous message: [Python-3000] C API for ints and strings
- Next message: [Python-3000] C API for ints and strings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]