Re: mdb2 game plan

From: Date: Sun, 27 Mar 2005 09:15:20 +0000
Subject: Re: mdb2 game plan
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-36891@lists.php.net to get a copy of this message
Daniel Convissor wrote:
While there are merits to splitting the drivers out, those aren't the reasons. All of the drivers extend from the same base class and provide similar functionality.
Well just because this has been the case in the past. Like I said its entirely possible to create a second set of pdo based drivers that exploit some of the functionality from MDB2 core. However obviously we will not get quite as low level as some CPAN modules might, as we have PECL for this purpose.
Basically, if one driver is stable, should it be marked as unstable because another driver is unstable?
Sure. So, make a note in the docs, driver, etc.
The problem is that for example I dont have the means yet to fix up the mssql driver and I havent had sufficient amount of time to fix the fbsql driver. This keeps delaying releases as I try to fix up these drivers and in the end dont get around to it. Also with subpackages I feel more comfortable in delegating leadership of the drivers to others, who then dont need to get spammed with core bugs unless they are interested. So yes obviously this could create 5-10 in the long term maybe 15 packages or more. But what is the problem here? Its not like my code size is increasing. Most drivers will be around 2k-3k LOC which probably rivals many packages in size. Next to phpdocumentor I think MDB2 is currently one of the largest packages out there. Furthermore instead of not having any dependencies on the given extensions because I refrained from putting in a zillion optional dependencies I could then start actually putting in the proper extension dependencies. While I can see this being more work for me in some cases (especially while I am still in beta), in the long run I can see this easing my work and the work of users where I can more easily push out a fix for a single driver instead of doing an entire new release for all of core as well (branches could help here too, but to me they make "fixed in CVS" kinda untransparent). Finally we have list-upgrades and upgrade-all. I dont know if there is a funky command that would enable upgrading of all MDB2 drivers in one go without typing them all out (a quick look in pear help upgrade/upgrade-all didnt show anything like regexp search). I also dont know how all this subpackage stuff is currently going to, if at all. So maybe these packages will just have a dep on a fixed MDB2 core version. Anyways: Whats so bad about having more packages? regards, Lukas

« previous php.pear.dev (#36891) next »