"Daniel Veditz" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> If you are distributing binaries you only need to find one person willing to > buy the Professional version of Kylix and that person could create non-GPL'd > binaries that could then be legally distributed when combined with MPL code. Unfortunately, this is not correct. From: http://www.borland.com/kylix/faqs.html ---------------------- [...] Furthermore, the Open Edition IDE End User License Agreement (EULA) also requires that any software developed with Kylix Open Edition must be released to the general public under the terms of the GPL. Any other use of Kylix Open Edition IDE would be in legal violation of the license agreement. [...] Q: If I use the Kylix Open Edition to evaluate the product, is any code I touch with it affected by the GPL? A: Only if you deploy applications built with Kylix Open Edition. Deployment happens as soon as source code or binaries are transferred to another person. In other words, if you have a team of five programmers working on a commercial product that will be shipping with a non-GPL license, then each programmer must have a copy of either the Kylix Desktop Developer or the Kylix Server Developer in order to work on the same project. However, if you are simply evaluating the product and you build some reusable code that you do not deploy, you can rebuild it with the Kylix Desktop Developer or Server Developer editions for proprietary release. ------------------------ This would suggest that any source code you create/modify in Kylix OE and transfer to somebody else, is automatically GPL code, and the other person cannot just compile it and release under MPL.. -- Michael Beck http://www.geocities.com/beckmi/delphi.htm Project JEDI - http://delphi-jedi.org 2001 "Spirit of Delphi" Award Winner
