Re: dependencies and applications

Davey wrote:

Just tossing this into the air. This *really* seems like the least messy, easily implementable (its all on the individual package developers, and if they don't publish a new version of something by PEAR 2.0 perhaps it should be moved to siberia anyways), backwards and forwards compatible solution with the most amount of migration time. - Davey

And so, thanks to pierre (I mean that sincerely pierre :) we have the first flaw in my idea: the pear command is not currently able to let you specify the version to install. Also, there may be needed updates to pear web for this too. (i.e. pear.php.net/get/PEAR_Info/1.0 would get the latest release in the 1.0 branch). This means we cannot rush into these things (not that we would anyways!). We should slow down, and talk *specifically* how we can implement this feature (it should go in anyways IMO). We also need pear update* to be aware of seperate major versions too, and to never upgrade across major versions. As pierre also points out, there are other more pressing issues: * PHP 4.3.3RC4 - Wheres your tests results hmm? * PECL - Apparently there are issues here (with 4.3.3 only?) * "QA QA QA QA QA QA" - Pierre Can we now leave this thread to broil in our heads, and make sure we get this right. And in the meantime... QA! Please read the pear-qa list (or refer to http://news.php.net/article.php?group=php.pear.qa&article=149) for that needs to be done. Lets make 4.3.3 or first QAed release and get it right. We've (me and pierre) already fixed two bugs in go-pear.php in our mini-QA session, I'm sure theres more to find too :D - Davey