Re: mdb2 game plan

Lukas Smith wrote:

Daniel Convissor wrote:

Splitting each driver out sounds like a tremendous headache for maintaining, installing, etc.

well the main advantage is in having separate release cycles and states for each driver. i think most people mostly use only 2-3 drivers. also some drivers like the ibase driver are maintained entirely by lorenzo. i am kinda hoping that one of these days someone takes over the resonsibility of the fbsql or mssql driver who are severely lacking in stability. i also forsee new drivers being added for maxdb, or maybe an additional set of drivers based on pdo. so the number of drivers could get fairly large.

I have to agree with Lukas. Don't forget that in package.xml 2.0, you can make all the drivers install by default. <dependencies> ... <group name="default" hint="all drivers"> <package> <name>MDB2_driver_mysql</name> <channel>pear.php.net</channel> <min>whatever is the minimum version</min> <recommended>recommended version</recommended> </package> </group> etc. If you also provide groups for each driver, the user can then choose to only install MDB2 and the mysqli driver, for instance. Also, those depending on MDB2 who only need 1 driver can use the <nodefault/> tag in their dependency to avoid automatically installing the default install group, and instead directly specify the driver packages they need. To me, it looks like a great design choice, and it kills one of the primary criticisms I've heard about PEAR from non-PEAR devs (bloat) Greg