> If you are distributing a product to others that includes GPL > software, and you don't want to put your own work under the GPL, the > end-user has to download the GPL package separately (e.g. MySQL) and > then plug it in. (And you also have to be careful about how the > plugging in process works.) If you distribute the product as a > ready-to-go bundle, then the viral aspects of the GPL kick in, and > your package must be GPL too. :( > > -Ted.
Not strictly true. You cannot distribute it as a single program. But you can distribute it together. Take a java web-app using mysql. You can compile it and build a war (excluding the jdbc driver). This program is therefore NOT including any GPL code (as long as you havnt used any elsewhere), and not affected by the GPL license. If you distribute it on a cd, with mysql and the jdbc jar on the cd, then you are not breaking the rules, as the programs are separate. See: http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation You could probably get away with writing install scripts that install your package, the mysql package, then install the extra jar. Note that once the programs are combined again, they would break the rules if distributed again with the jar file intact. Daniel. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
