RE: [PHP-DEV] readline extension status?

> James Moore wrote: > > the same. I could see problems if we were commercial and they > were OS but > > thats not the case. We are all OS, would we have a problem, > licience wise > > (Maybe Zend would) if Apache started distributing PHP in its > releases, it > > wouldnt make a difference to our licience.. it would still be the same. > > I'd take it serious, though. The Gnomes and Gnus were at Jihad > against Qt for several years, and that was no fun at all. You'd > rather not want to have a "PHP === evil" on /. at all, that would > be _really_, _really_ bad publicity. OK well lets find out which incompatibilities there are problems with (IE contact people ask if they have a problem with our liciences etc..) then check the legality of what they say (or even better yet try to get the original author to check it that way it costs us nothing :). There are various extensions I think that we will have no problems with (mcrypt, mysql), if we have lots of legal problems could we not look at adding a cluse to the PHP licience saying some modules are distributed under different liciences etc and see the licince file in the individual directory. IANAL but I cant see how writing code that interacts with certain libaries is illegal when their liciences are not compatible with ours. Its a loss on both sides if it ends up with not being able to resolve this (If anyone here has some legal training perhaps they could set us straight). James