Re: Re: where did phpunit go?

I'm guessing this situation implies a need for a general procedure to handle packages that relocate themselves from PEAR, so that handling each one is not a case-by-case "patch", as well as advertising to current packages what PEAR would plan to do if a package decided to move away. I'd say draw up a procedure that handles the general issue, with the first test of said procedure to be handling the PHPUnit issue. Not being deeply familiar with PEAR's inner workings, I'm again guessing that such a procedure doesn't already exist, given the dialogue so far. Chuck On 2/21/07, Bertrand Mansion <golgote@mamasam.com> wrote:

Le 21 févr. 07 à 15:47, Arnaud Limbourg a écrit : Just add the package home page with a BIG message to indicate the move. That is really all we need. You don't build a dynamic website of this size with patches applied here and there. It is better to get rid of the exception, unless it becomes the rule. That's just my opinion. -- Bertrand Mansion Mamasam Work : http://www.mamasam.com Blog : http://golgote.freeflux.net -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php