Distribution of .dll files within PEAR (and announcement of php_imagick.dll)

Hi had some quite minutes today and compiled imagick on windows. After some adjustment it runs now also on windows.. You can download it from http://php.chregu.tv/php_imagick.dll (you need also the imagemagick libraries available from http://imagemagick.org). Hope this helps the folks, which do use Windows :) Therefore I'm wondering how binary modules should be distributed within PEAR. IIRC, there's the role "ext" which installs it in the extension directory, but I would prefer a mechanism which allows to upload binary extensions seperated from the source. For example, I don't have a windows-compiler at hand all the time and could not upload a new source package then without having to compile it on windows (or having inconsistences in the uploaded packages) and it (approx.) doubles the download-size for people, who don't need the binary. just my 2 cents once more :) chregu -- christian stocker | bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | chregu@bitflux.ch | gnupg-keyid 0x5CE1DECB