Background, to make life easyer for people that use more versions of
mysql (and just for fun) MySQL is going to be slotted.
Currently the slot enabled versions are mysql-4.1.16-r30
mysql-5.0.18-r30 mysql-5.1.4_alpha-r30, in short those with "-r30".
The few patches needed are already included in current ~ mysql-4.1.16
and mysql-5.0.18 but hidden due to SLOT=0, starting from 2005-11
An eselect-mysql module has been prepared to create simlinks for the
desired version of mysql making easy to switch between them (hopefully)
The libraries (libmysqlclient & co) don't follow this logic and the
higher version is always the default (similarly to sys-libs/db).
The rc-scripts have been modified to use the logic of
sys-apps/baselayout net.ethx => net.lo symlink to be able to start more
servers at once (this is working from 2005-11 but reworked today)
Additionally the ebuilds code has been moved to two new eclasses,
mysql_fx.eclass and mysql.eclass, the first own support functions, the
last own the src_* pkg_* functions.
The initial idea is that when a specific ebuild need to marked stable
the code is moved from the mysql.eclass to the ebuild itself, to froze it.
Documentation on:
o switch to slotted
o upgrade with no downtime using this new capabilities
need to be written from scratch (this is going to be the more difficult
part for me).
there is a bash construct the eclass use to retrieve the latest two
chars of a string, in the form: MYVAR="${MYARRAY[3]:(-2)}" , is this
acceptable?
The intention is to made mysql-5.0.18-r30 stable on 2005-02-15 at
maximum on the first archs.
AFAIK I'm the only one who have seen this stuff until now, any comment,
any suggestion is highly apreciated.
Francesco Riosa
--
gentoo-dev@gentoo.org mailing list
