Michael van Elst 15ab2e8eeb and fix typo in specfile il y a 22 ans
..
my.cnf 0ead80fc67 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. il y a 22 ans
my.pwd 0ead80fc67 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. il y a 22 ans
mysql3.patch 0ead80fc67 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. il y a 22 ans
mysql3.spec 15ab2e8eeb and fix typo in specfile il y a 22 ans
rc.mysql3 0ead80fc67 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. il y a 22 ans