Does translating a library into another language make it a “derivative work” for the purposes of GPL/LGPL? -
i developing iphone application use existing code published under lgpl. because of nature of apple’s app store application not open source , charge amount (either $0.99 or $1.99) in order cover expanses publishing in store. have studied lgpl , know allows use of code proprietary software if using library. however, code in question written in javascript need convert objective-c, believe make considered “derivative work” , guess requires must open-sourced (please correct me if wrong). question if translating library language makes “derivative work”, , if enough open-source library, or must entire application using published under lgpl well?
i have sub-question. there exists previous version of library has been translated several languages, including objective-c. however, written while library released under gpl (which prohibits using in closed-source software). in mean time license changed lgpl (for original javascript version), affect translated versions or still pure gpl?
so question if translating library language makes “derivative work”
yes.
and if enough open-source library, or must entire application using published under lgpl well?
if good-faith translation (i.e. without other changes), library needs open-sourced.
in mean time license changed lgpl (for original javascript version), affect translated versions or still pure gpl?
any translation or other derivative work based solely on version x of software not affected licenses of other versions of software, earlier or later. yes still gpl, unless explicitly changed.
this not legal advice , i'm not lawyer.
Comments
Post a Comment