The general public menu pdf license only requires software under the LGPL be modifiable by end users via source code availability. LGPL, but not for any proprietary components.
1991, and adopted the version number 2 for parity with GPL version 2. The LGPL was revised in minor ways in the 2. 1 point release, published in 1999, when it was renamed the GNU Lesser General Public License to reflect the FSF’s position that not all libraries should use it. Version 3 of the LGPL was published in 2007 as a list of additional permissions applied to GPL version 3. Whether a work that uses an LGPL program is a derivative work or not is a legal issue.
It would fall under the definition of a “work that uses the Library”. Paragraph 5 of the LGPL version 2. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. Essentially, if it is a “work that uses the library”, then it must be possible for the software to be linked with a newer version of the LGPL-covered program.
3 of the LGPL version 2. This feature allows for direct reuse of LGPLed code in GPLed libraries and applications. Version 3 of the LGPL is not inherently compatible with version 2 of the GPL. GPLv2 “or any later version” may be combined with code from a LGPL version 3 library, with the combined work as a whole falling under the terms of the GPLv3. The former name “GNU Library General Public License” gave some the impression that the FSF recommended software libraries use the LGPL and that programs use the GPL. Which license is best for a given library is a matter of strategy Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it When a free library’s features are readily available for proprietary software through other alternative libraries the library cannot give free software any particular advantage, so it is better to use the Lesser GPL for that library.
Stallman and the FSF sometimes advocate licenses even less restrictive than the LGPL as a matter of strategy. LGPL with this preamble is sometimes referred as LLGPL. GMGPL-covered units without the code itself becoming covered by the GPL. Version 3 of the LGPL addresses such cases in section 3. The LGPL does not contain special provisions for inheritance, because none are needed. Inheritance creates derivative works in the same way as traditional linking, and the LGPL permits this type of derivative work in the same way as it permits ordinary function calls.