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