IANAL (and correct me if I'm wrong), but.... 1) Parts of WebKit are licensed under the LGPL 2) Even if you're not modifying (or copying code from) files licensed under the LGPL, any files linked to those LGPL files are governed by the LGPL 3) Presumably you're going to distribute binaries that include your modified version of WebKit 4) And thus aren't you compelled to release the source code for anything linked to any LGPL whenever 3 happens?
If so, why not just develop in the open? J On Wed, Jun 17, 2009 at 1:56 PM, Toshiyasu Morita <[email protected]>wrote: > --- On *Wed, 6/17/09, Geoffrey Garen <[email protected]>* wrote: > > > I'm not really interested in helping with the dubiously legal task of > taking > > JavaScriptCore, which is an OpenSource library, and turning it into a > closed, > > proprietary library. > > I'm not sure where this weird idea of developing a "closed proprietary" > library came from. I have never mentioned anything about developing a closed > proprietary library. > > My client is a hardware company. It produces consumer devices. They have > been using GNU software for a long time. Their current website has a support > download page where you can download the GNU source code used in all their > released products. > > Toshi > > > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
