After a long enough evaluation phase, we've now officially moved in
OpenPKG-CURRENT from MySQL 3.x to MySQL 4.x.
Following our general rules for dealing with versioned packages (and
the fact that we only want _one_ single version in each release, of
course), the old (MySQL-3 based) "mysql" package was first merged up to
1-STABLE (for possible inclusion into OpenPKG 1.3), then "mysql" was
renamed to "mysql3" (in case you still have to drive MySQL 3 within
OpenPKG-CURRENT), "mysql4" become "mysql" and "mysql4" has gone.
So, if you're running OpenPKG-CURRENT and upgrading your "mysql"
package, be aware of the version jump. Whether OpenPKG 1.3 contains
MySQL 3 or already MySQL 4, will be decided later once we have enough
feedback for the OpenPKG-CURRENT "mysql" package.
Keep also in mind that those package renames are important for release
engineering and smooth transitions between releases, although for
OpenPKG-CURRENT drivers they can be boring during upgrading (if they
want to stick with the old version they now have to move from "mysql" to
"mysql3" -- or if they already ran the new version, then they have to
move from "mysql4" to "mysql"). But that's the price we all have to pay
in OpenPKG-CURRENT...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
