Davey wrote:
Greg Beaver wrote:
Davey wrote:
One thing to mention, doesn't changing all these things mean breaking
BC in PEAR? (I know that you could easily break PEAR_Info :) Which
means this should be put into PEAR2 only, much as I hate to say it as
it might mean we can't have channels till PEAR2 :(
No, for the wonderful reason that PEAR_PackageFile will have the
ability to return the exact array that PEAR_Info desires. Plus, older
PEAR_Info will be using the PEAR_Common::infoFromString() crap, which
will maintain BC. However, it will mean that until PEAR_Info is
upgraded, the newer features of package.xml/channels will be unavailable.
You know I'm a BC hound dog :)
Greg
PEAR_Info doesn't use these, I use the PEAR_Registry, IIRC.
PEAR 1.4.0 fully passes the existing PEAR_Registry unit test, and this
was a big requirement for me - the existing API is 100% BC, and channel
is always an optional, extra parameter. PEAR_Config is almost exactly
the same way, although I had to rewrite the unit test in order to
account for some of the internal changes. The API is BC, however.
Greg
--
PEAR Core List Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
|
