Questions about Pyrus, and other things

Hello, Some of you mention "Pyrus", now and then - but it's still a mysterious horizon for me, in spite of what I read on some blogs. Could someone shed some light on Pyrus and PEAR2 for me please? 1. Is Pyrus designed to work *only* along with PEAR2? 2. When will PEAR2 CS apply? As soon as PHP 5.3 and Pyrus are released? 3. How is the migration from PEAR1 to PEAR2 conceived, regarding the existing packages? Should the current packages "choose their side"? 4. Why doesn't the PEAR2 HTTP_Request example use any namespaces? (I thought this was one of the major changes) [5. BTW, not a PEAR question, but there are guys from internals here, so they certainly know the answer: why can't we import a whole namespace, like: "use PEAR2::HTTP::*" ? Is it a performance issue? Just out of curiosity... ] 6. What about packages that have their own autoloading mechanism? I read that "spl_autoload_register() registers functions in the order that spl_autoload_register() was called", so I guess the PEAR Autoloader will always have precedence over any package autoloader. Thus, if some code calls the class PEAR2::PHP::UML::Metamodel::EMOF, the Autoloader will load it from PEAR2/PHP/UML/Metamodel/EMOF.php, right? 7. Some of you talk about "svn external"... Which role does that SVN thing play in the PEAR2 system?? Thanks for the enlightenment! Baptiste (a naïve developer)