Re: Questions about Pyrus, and other things

Brett's answer look pretty good on #4 (http request namespace) namespacing is waiting for Travis's namespace (and mine i guess) rfc to get finished so I don't have to change things multiple times. Also i've been extra busy lately. on #6 (custom autoloaders) We would expect all packages to follow the same naming conventions so there shouldn't be a need for more then 1 autoloader for pear2 on #7 (svn externals) we also use svn externals to give you any easy way to checkout all the trunks of the sub packages just svn co http://svn.pear.php.net/PEAR2/all/ Brett Bieber wrote:

Greetings, On Tue, Jul 22, 2008 at 5:23 PM, Baptiste Autin <baptiste.autin@free.fr> wrote:

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?

I'll take the easy ones.........

1. Is Pyrus designed to work *only* along with PEAR2?

Pyrus can install PEAR(1) packages with v2 package.xml as well as PEAR2 packages.

2. When will PEAR2 CS apply? As soon as PHP 5.3 and Pyrus are released?

CS in PEAR2 will be pretty much the same... there were some proposed changes and additions (http://wiki.pear.php.net/index.php/CodingStandardsChanges), but I don't believe these are official yet. If you're referring to the PEAR2 Standards (http://wiki.pear.php.net/index.php/PEAR2_Standards), those apply for all PEAR2 packages, not PEAR1 packages.

3. How is the migration from PEAR1 to PEAR2 conceived, regarding the existing packages? Should the current packages "choose their side"?

Much of this is yet to be determined... I don't think people need to choose sides, but I hope people maintaining the top packages in PEAR1 are considering a PEAR2 version of their packages.

4. Why doesn't the PEAR2 HTTP_Request example use any namespaces? (I thought this was one of the major changes)

I think we've been waiting for the dust to settle on namespaces... up until recently all the code worked on the latest PHP release (5.2.5,5.2.6) - which meant you could work on all the code without relying on a 5.3.0 snapshot. Now that we're so close to 5.3.0, I think we can start moving the code over.

7. Some of you talk about "svn external"... Which role does that SVN thing play in the PEAR2 system??

The svn:externals property allows developers to track the svn versions of packages within their own repositories. Now that PEAR2 packages are in svn, developers can use svn:externals to track individual packages or the entire repository along side the files in their own repository. That's all it means for PEAR2 currently, unless you have some specific questions about the RFC (currently a draft) that Travis is working on (http://wiki.pear.php.net/index.php/PEAR2_Naming_Standards) - and how that may affect PEAR2 packages. Hopefully someone else can answer 5 and 6, or give better answers than mine for the others.