pecl stuff and overall documentation

Hello As you maybe know, I started coding an ImageMagick extension for php (more information at http://php.chregu.tv/imagick). But now to the main part. I was told at php-dev (and i heard it here as well), that no new extensions should go into the php4 source tree instead they should go to pear. I have no problem with that, but i think pear is not really ready for that. Is the PECL-Dir really meant for that? (I think i missed something about that..). Moreover the PEAR::Installer is already quite useful for PEAR-Classes, but for traditional extensions, it fails. Maybe an option to state ones php4 sourcetree and the pear::installer copies the requierd files directly to the ext/ diectory would be a good idea for the moment (and shouldn't be to hard to implement). later we can use the post/preconfiguration stuff for making self-contained extensions (at least on systems with a compiler...). A IMHO really good solution would be, if the ./configure script of php4 would get the needed extension automatically, ie. if i write ./configure --with-mysql it gets the latest matching mysql stuff from pear/pecl. but that's maybe a little bit too much for the ./configure system... but if we would have something like that, more extensions from php4 could go to pear and the whole php4-tree wouldn't be that bloated as it is now (ask the qa-group about that :) ) One more remark, discussed already many times, but how's the documentation now handled. there are this 2 alternatives that every package has the documentation in his own directory and it's browseable with the "Package Browser" on pear.php.net, or we have the same system as with php -> one big peardoc directory with the xml files, where all the writers have access. and it looks like martin already did something like that on the webpage, unfortunately the xml-files for that are missing, otherwise i would have added the doku for the imagick extension already ;) that's it for the moment. now you can fight over it :) chregu