Quoting Andy Sy ([EMAIL PROTECTED]): > It's a different kind of license, I suppose. As far as I can tell, > LGPL allows you to link to an LGPL'ed module without open-sourcing the > product being linked. That's the common sense assumption, but Rick > Moen may have something additional to comment on that.
No problem: LGPL puts no restrictions on dynamic linking. (No, not just LGPL only.) "Static linking", i.e., compling the code directly into the binary, of code under licence that restricts user rights to fork, etc., creates a licence conflict that would prevent you from lawfully distributing the derived work. However, the best way to understand any of these licences is to _read them_. > With Firebird's MPL style license, my common sense interpretation is > that you only have to open source your mods that have directly to do > with the MPL'ed code. Correction yet again: You don't "have to open source" anything. You can only lawfully redistribute works derived from other people's MPL-covered modules if you comply with the MPL source-access (and other) provisions as to that module. You keep drastically overstating the obligations upon developers, in each of these cases. Even after repeated corrections. Is there a reason why? > Best clarification of course would be to explain your particular usage > scenaro to the firebird people at the news.atkin.com ib-support > newsgroup. No, best clarification is to _read the licence_. -- Cheers, "I don't like country music, but I don't mean to denigrate Rick Moen those who do. And, for the people who like country music, [EMAIL PROTECTED] denigrate means 'put down'." -- Bob Newhart _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
