> > MySQL's license has strings attached, you can't use it for free > > if you don't want to release your source. > > ..._and_ you distribute binaries, _and_ you actually link to the MySQL > codebase as opposed to merely using it, _and_ you haven't haven't > negotiated a licence exception from the copyright owners.
Yes, of course, should have been more explicit there. I meant to say you need a commercial license if you write an app that _links_ with MySQL and don't want to release your sources. Actually, with MySQL, there are a few more strings attached than mentioned here or at least there were when I checked out the MySQL site a few months ago. They may have clarified things since. > > License-wise, Firebird uses a Mozilla style license which > > as I understand it means that you only have to release > > source on those parts you modify which have to do directly > > with Firebird. > > Again, you are in error on the "release sources" concept. Copyleft > licences such as GPL and MPL trigger obligation of source code access > only if you distribute binaries. (In the case of MPL, licence > provisions apply separately to individual code modules.) As far as I can tell, MPL-style copyleft licenses are less strict on which parts of your source code you have to release. GPL requires you to release full sources to anything that even uses a teeny bit of code from a GPL'ed module (such as readline). Whereas MPL, again as far as I can tell, as IANAL, only requires you release as source those modifications that have directly to do with the MPL'ed module. _ 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]
