3 ms·
LGPL has nothing to do with API, but rather the definition of a derivative work. Using a library i akin to put a engine into a car. One could argue that the en
by belorn 13y ago
LGPL has nothing to do with API, but rather the definition of a derivative work.
Using a library i akin to put a engine into a car. One could argue that the engine would still be a separate piece and thus not "part of the car", but its a tough sell to do in court. The line that separate "a thing" with "other things" is determined by judges, juries (and in some cases, common sense). In 23 years, no one has dared yet to do so.
Using an API however is like putting your own engine into the car, but it happens to use the same input/output of similar car engines. The GPL do not have a dog in that fight, but FSF argues against such stretching of copyright.