Re: more candidates for PECL

Can we add a notice into the configure script in 5.x when using these extensions and move them into PECL for 6.0? A hint in 5.x will inform the few people who are using the extensions that they will find them in PECL in future. Maybe current configure options like "--with-hwapi" will be kept and print an error message about moved extension. This would help those people, who take old configuration options to recompile new version. mike Richard Lynch wrote:

On Mon, April 24, 2006 4:47 pm, Antony Dovgal wrote:

I'd like to propose yet another bunch of extensions to be moved from core to PECL. (Don't worry, this is for 5.2 and HEAD. 5.1 is untouchable atm).

I just think the timing should be on a major release (6.0) and not a minor one (5.x) since the changes to code-base seem rather large and wide-sweeping, even if the functionality and userbase are believed to be negligible. Why tick off that one developer by "removing" functionality in an upgrade, when that's only supposed to happen in a major release? jmho

-- mike peter bretz metropolis ag / entwicklung email: m.bretz@metropolis-ag.de heinestraße 72 phone: +49-7121-348-120 d-72762 reutlingen fax: +49-7121-348-111 http://www.metropolis-ag.de/ metropolis ag. creating social internetworks.