Hi Francesco,
Francesco Riosa wrote:
The idea is to leave the people free to choose mysql 4.0 or 4.1 and continue to build all their usual packages (there are incompatibilities between the two versions that break a lot of builds).
This solves the problem for people who really want multiple versions of MySQL installed simultaneously, but what about the people (like me) who *don't* want multiple versions, and just want a single, working MySQL - preferrably the latest stable release?
Also it seems to me that you cannot have the different MySQL's pulling from the same set of files for database access because:
a) a newer version might create files on disk incompatible with older versions of MySQL
b) If you're installing different versions, you ought to be able to run them simultaneously
So that means MySQL's data files have to be installed into a different location for each slotted version of MySQL. Given that the typical user wants just one MySQL that just works, to upgrade across slotted versions they'd have to mess around copying/moving files in /var/lib/mysql.
As I see it, SLOT makes sense for things than can easily coexist and/or are imcompatible with each other - GTK1 & GTK2 and Apache1 & Apache2 are good examples - but how many users *really* want multiple MySQL's installed? Wouldn't this be about like having multiple versions of Perl installed?
Wouldn't it be better for almost everyone to work on fixing those packages that break, so that unmasking 4.1.x is a possibility, instead of making everyone deal with SLOTs?
-- Jason Rhinelander -- Gossamer Threads, Inc.
-- [email protected] mailing list
