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