Honestly, I don't see why is this needed. It works the same way like apache slots or php slots or whatever other slots. If users emerge an ebuild explicitely, they get the highest version available, if they want something else, they can do
"echo >=dev-db/mysql-5*" >> /etc/portage/package.mask" That's exactly the same amount of user intervention required as if they should enable multislot use flag in package.keywords instead (considering that users definitely don't want to enable such flag globally for things like binutils or gcc). Also, the current behaviour doen not take away the possibility for other ebuilds to depend on a specific slotted mysql version, e.g. if something doesn't work with 5.x but works just fine with 4.1. That won't be possible once multislot use flag is required for slotted install. -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;)
pgpfEOpvV3PGc.pgp
Description: PGP signature
