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

Hi Greg, Each different extension provides a PDO driver with a different name (the idea is that it is theoretically possible to load all three different implementations into a given process and make use of them). From a packaging perspective, you'll probably use either a dep on the package PDO_DBLIB to express that you're compatible with any one of those flavours of dblib, or a dep on the specific extension that you're compatible with. PDO_OCI, on win32, can build php_pdo_oci.dll and php_pdo_oci8.dll which are identical except that php_pdo_oci8.dll is linked against an older version of the OCI libraries. In this case, the driver name is the same, so you can only load one version or the other into your process. --Wez. On 9/24/05, Greg Beaver <greg@chiaraquartet.net> wrote: > Wez Furlong wrote: > > >PDO_DBLIB can generate one of three different extensions, depending on > >the options that are passed to it's configure script. > > > Hi Wez, > > This is *extremely* useful information, thank you. I did not anticipate > that a single package could or would supply more than one extension > possibility > If a package depends on pdo_dblib, does it matter which actual extension > is enabled, or is the only difference system-dependent? In other words, > from the perspective of a package that uses PDO, if you depend on the > pdo_dblib package, is there a difference in depending on the mssql > versus the dblib or sybase extension? > > If not, I will simply amend the xsd for package2.xml to allow multiple > extensions to be provided, and update dependency checking to cycle > through all extensions listed when checking for installation. > > Greg >