Chris Gianelloni wrote:
On Wed, 2005-01-12 at 03:29 +0100, Thomas de Grenier de Latour wrote:
On Wed, 12 Jan 2005 02:32:34 +0100
Francesco Riosa <[EMAIL PROTECTED]> wrote:
my bad explaining, /etc/init.d/mysql is the *same* (md5 sums)
for all mysql versions
That's still not good imho: some people use
CONFIG_PROTECT_MASK=/etc/init.d (I do for instance). In such a
case, uninstalling one of the slotted mysql package may remove the
initscript (if it is the latest emerged one that is removed,
because mtime will also match).
I think a better approach would be to have one real file
initscript per SLOT (/etc/init.d/mysql-${SLOT}), plus an
/etc/init.d/mysql symlink pointing to the one with the greatest
version for lazy people and backward compatibility. You can
probably use the alternatives.eclass to manage this symlink btw.
I was thinking a better idea would be a mysql-launcher ebuild which
installs only this init script. All the mysql versions could depend on
it and symlink to the init script created by it.
yes, and the same ebuild will do some other stuff (FIXME go deeper),
hopefully not to reaching the complexity of gcc-config or opengl-update.
--
[email protected] mailing list
