Re: disabling dead pecl extensions from pecl install

Johannes Schlüter wrote: > On Sat, 2009-04-04 at 10:45 -0500, Greg Beaver wrote: >> if people shouldn't install it, then remove the package. Otherwise, why >> have it? > > For historical reasons. It's nice to have old releases somewhere, > sometimes. > >> Alternately, set the maximum PHP version in the php dependency, and the >> installer will refuse to install it for newer PHP versions. > > Then one has to make a new release which does nothing but prevent > installation, no? Would be nicer to set this in the Web-GUI. Hi, As Pierre said, he will do it in the web. Fortunately, for those doing a simple "pecl install ****" the data used to validate dependencies is downloaded from REST serialized at pecl.php.net. So, one could actually change the php dependency in that serialized info and then it would affect installations without a new release. Best would be to add the <max> tag in package.xml inside existing package, perhaps with a simple phar script <?php $package = new PharData('/path/to/sqlite-1.2.3.tgz'); // 1.2.3 should be the real version obviously $info = $package['package.xml']->getContent(); // add the <max> tag in $info where it needs to go $package['package.xml'] = $info; $package2 = new PharData('/path/to/sqlite-1.2.3.tar'); $package2['package.xml'] = $info; ?> This would ensure that if the REST ever needs to be regenerated from the database/released tgzs, it will still be valid. Greg