On Wednesday 12 January 2005 10:47, Francesco Riosa wrote: > > Done it between 4.1 e 5.0, with myisam tables, and also between mysql > 4.0 and 4.1 a long time ago, do it is possible but not grantable. In > every case enable external locking is necessary. > > > 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. > > Not sure, for the present I can make some test, in every case we can't > be sure for the future. > > > 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? > > I think that developers that interfaces with databases want it. Server > administrator may want it to try and to upgrade in a more smoth way. > End user may want to have a simply "dev-db/compat-mysql" or something > like that. > > > 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? > > There are *hun�dreds of packages that can break, it's not a trivial > task and it's long, also it limit you to 4.1 why not to have the > possibility to try 5.0 ? > *
Being responsible for slotting up sys-libs/db so db-4 could be introduced I must warn you from the hell that you are going to put on yourself allready when providing multiple slotted versions. Every ebuild that links against mysql needs to be checked on whether it correctly gets the wanted mysql, and not headers from one, and the library from the other version. In any case having two database engines providing the same database is a bad idea, as even if it technically works (which is iffy), it would make any caching performed be invalid. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgp65yqRYFnt4.pgp
Description: PGP signature
