3 ms·
These are patches to the LGPL'd components they use, not Sparrow itself, right? (The LGPL specifically requires that you only release your modifications to the
by geofft 14y ago
These are patches to the LGPL'd components they use, not Sparrow itself, right? (The LGPL specifically requires that you only release your modifications to the library, not your own code.) The only interesting things are some images, and some patch files inside lib/ -- nothing appears to be Sparrow's own source code.
It looks like they also toss in some compiled versions of Sparrow-proprietary code for debugging reasons, which I _think_ explains their incongruous licensing terms, but they're still strange.
- saurik 14y agoThe LGPL requires you, if you static ally link against such libraries, to release all of the rest of the build environment required to rebuild a working program from changed LGPL components; this involves releasing binary objects.
- alok-g 14y agoDoes it require the entire build environment (as in all the tools used for building) or just the binary objects? In other words, do the build scripts become subjected to the LGPL?
- DannyBee 14y agoNo. The LGPL requires you release them, it does not require you release them under the LGPL.