AFAIK the licence is on a per file basis, and not per project. The only licence you need to worry about is what licence you give to your code as cake will stay MIT, TinyMCE with stay the licence it is released under.
On 23 Oct, 14:34, pepejose <[EMAIL PROTECTED]> wrote: > hello again. > > I opened this post because I am making an application that I have to > release as open source (I'm not forced to use a specific license) > > My situation is as follows: > > ** Cakephp 1.2 RC3 -> MIT > ** My code (views, controllers, models etc) -> GPL? > ** Some code with LGPL (tcpdf, for example TinyMCE) > > then, which is the best way to publish the application in one package? > > diferent licenses? > > On the one hand I read that MIT, GPL and LGPL are compatible but on > the other that if I use GPL code in part forces me to use GPL code in > all code ... on the other side as section 3 of the LGPL can convert to > LPG but i dont know not changes that I have to do exactly > > greetings and thank you very much > > PD: forgiveness for my English --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
