Re: PECL versioning

Hi Rasmus,

It's not illegal, but we would have to follow the EAR rules and we would have to do something along the lines of the ASF page here: http://www.apache.org/licenses/exports/ Since we are not a predominantly US project, nor does PHP itself contain any sort of crypto code or anything that could be classified as sensitive, at the PHP source level we can get away with not doing this EAR crap. At least that's my stance on this stuff. However, once you start building binaries that may or may not pull in 3rd-party stuff and redistributing those you then have to start worrying about what is in that code. That's one of the main reasons I have never been that keen on distributing binaries of any sort and instead hand that off to the various OS distributions to deal with. My preference would be to keep things clean and not build and distribute binaries from any US-hosted machines.

OK, bye bye Easter project :) But at least now I've hit the first two practical problems and we all know what needs to be done to resolve them cleanly, and both 'fixes' could be started without the need for much further discussion. I'm making a list, but I'm only up to H... I'll post it somewhere (wiki? - this sounds like a wiki-ish thing) in table format when it's done. Just looking at who's using what in zend_module_entry and if there's a version defined, where it's defined. - Steph

-Rasmus -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php