News for hackers. Stuff that matters.
Re:Sparrow made downloadable to conform to LGPL by geofft on Friday July 27, 2012 @02:47PM (#4302982)
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.

Re:Sparrow made downloadable to conform to LGPL by saurik on Friday July 27, 2012 @03:04PM (#4303060)
The 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.
Re:Sparrow made downloadable to conform to LGPL by alok-g on Friday July 27, 2012 @03:30PM (#4303196)
Does 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?

Re:Sparrow made downloadable to conform to LGPL by DannyBee on Friday July 27, 2012 @04:52PM (#4303527)
No. The LGPL requires you release them, it does not require you release them under the LGPL.