Re: mdb2 game plan

Lukas Smith wrote:

Hi, ok so here is the game plan .. with the next release I will split off MDB2 into the following packages: MDB2 - 2.0.0beta4 beta MDB2_Extended - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Schema 0.1.0 beta (used to be MDB2_Tools_Manager) depends on MDB2 2.0.0beta4 MDB2_Driver_mysqli - 0.1.0 beta depends on MDB2 2.0.0beta4

Let's see an imaginary user case: $ pear list mdb2 2 mdb2_mysql 0.1 (mdb2_mysql depends on mdb2 2) $ pear upgrade mdb2-3.0.0.tgz $ pear list mdb2 3 mdb2_mysql 0.1 For not breaking drivers deps, the mdb2_mysql package would need very complex deps like: mdb2 greater than 2 mdb2 less than 3 (and be very strict about break drivers API compat) If you choose to go for mdb3 instead, we'll get soon tons differents packages: mdb2, mdb2_mysql, mdb3, mdb3_mysql, ... I personally wouldn't go for that admin mess, I'd preffer something like mention the drivers state in the changelog of each release, or perhaps at the main package description. Subpackages is a cleaner way to go, but dunno how ended that war ;-) Tomas V.V.Cox