Re: Re: disabling dead pecl extensions from pecl install

Hello, Are there any opinions on this? It appears a someone recently deleted all of 'pecl/pdo' from SVN but that's not really a solution. Another less than ideal solution available today is to remove releases via the interface, which essentially hides the tgz files. Not sure exactly what that does but after deleting the single pecl/mysql release, 'pecl install mysql' no longer works (which is good). However, doing this feels dirty. Regards, Philip On Apr 10, 2009, at 11:25 PM, Philip Olson wrote: > > So to clarify, is the following going to happen? > > 1. People are told to use the <max> attribute in package.xml when necessary which may be: > A) When a pecl extension is killed and moved to core (typically) > B) When a core extension is killed and moved to pecl (depends) > C) When we determine an extension should not be used (always) > 2. The 'other' data 'pecl install' uses can be edited via the web interface > 3. A hack to edit package.xml of the last release and insert <max> will be added via the > web interface > > And Pierre, are you adding all or some of these things? Not sure about #3, it seems a little > scary but maybe it's fine. > > Also, do we want the ability to remove some of these packages from the package listing? > I'm referring to here: > > - http://pecl.php.net/packages.php > > Maybe an additional package listing named something like POO (Pecl Of Old). :) > > Regards, > Philip > >