Re: How many pecl packages have an different extension name from the package?

Wez Furlong wrote: >This sounds ok to me. > >The <providesextension>s are more like a "<mightprovidesextension>" >for PDO_DBLIB; so long as the installer doesn't assume that all three >are going to be there after installing the package, I think we're ok. >(do we need a way to specify this in the xml?) > heh, <mightprovidesextension> :) If the three extensions provide the exact same functionality from a user's perspective, does it even matter? In other words, the public API of PDO_DBLIB is identical between the three extensions, right? Is there any situation in which a user would want to use some extension-specific (as in mssql/sybase/dblib-specific) functionality, or is it just a question of how the thing is built? If the extension name is non-deterministic, it makes depending on it automatically just about impossible. Unless the answer to my question above is "yes it matters" I am not worried though Greg