| 1 |
Kalin KOZHUHAROV wrote: |
| 2 |
[...] |
| 3 |
>> |
| 4 |
>> An eselect-mysql module has been prepared to create simlinks for the |
| 5 |
>> desired version of mysql making easy to switch between them (hopefully) |
| 6 |
>> |
| 7 |
>> The libraries (libmysqlclient & co) don't follow this logic and the |
| 8 |
>> higher version is always the default (similarly to sys-libs/db). |
| 9 |
> |
| 10 |
> So how does this affect packages that use say dev-perl/DBD-mysql ? |
| 11 |
> |
| 12 |
> If they can only use mysql-5, then the will be broken if they connect to a mysql-4 server using non |
| 13 |
> UTF-8 encoding. (bad wording, but generally speaking, there is an inconsistence in character |
| 14 |
> encoding betweet mysql-4 and mysql-5 that DOES break things on non ISO-8859-1 encoded databases) |
| 15 |
> |
| 16 |
[...] |
| 17 |
|
| 18 |
At the moment 4.0 is not slotted, only >= 4.1 are. |
| 19 |
|
| 20 |
The fact that is effectively possible to use a non slotted 4.0 together |
| 21 |
with 4.1 and 5.0 does not mean that it should be used that way. |
| 22 |
|
| 23 |
Does this answer your question ? |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives