Re: Re: deprecating

From: Date: Wed, 20 Jul 2005 05:05:18 +0000
Subject: Re: Re: deprecating
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-38774@lists.php.net to get a copy of this message
Joe Stump wrote:
A better approach, IMO, would be to have package.xml enable developers to somehow warn a person about potential problems *before* pear installed the new package. For instance, pear would notice that I'm going from 1.0 to 2.0 and stop to tell the person upgrading that upgrading will cause X, Y and Z to break and to update their code, if needed, before installing.
Joe, This works fine in the single package upgrade scenario: $ pear upgrade X but breaks down when you upgrade a few packages, or you use switches like --onlyreqdeps/--alldeps or do Bertrand Gugger's insane: $ pear download-all $ pear upgrade *.tgz I am not saying that it is impossible, but I would encourage you to take a look at the internals of PEAR 1.4.0 and let me know what I have missed. To my eye, it seems to be extremely difficult or impossible to implement this feature without a removal of features like automatic dependency download/install or the ability to install multiple packages at once. Greg

« previous php.pear.dev (#38774) next »