Re: PECL versioning

Steph Fox wrote:

Hi Rasmus,

Note that there are some extensions we can't distribute from php.net in binary form due without doing the annoying export exemption paperwork. It wasn't an accident that pecl4win was a single non-US hosted machine.

Do we know which they are? If so we can mark them.

The obvious one is mcrypt. But any binary that links in crypto code is problematic.

Oh joy.

Here, read this: http://www.bis.doc.gov/licensing/exportingbasics.htm

Lovely... I think both Pierre and myself have servers in the .eu that could get around this, but it'd mess up the whole idea of having a central point for release binaries :( So basically we need to mark those and replace their download links on pecl.php.net with a note saying distribution is illegal from a US-based machine and to pick up a snapshot from pecl4win instead. (I assume that's okay?)

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. -Rasmus