Honza Horak wrote:
On 03/11/2013 12:30 AM, Rex Dieter wrote:
> 3. And long-term, what to do about MySQL-libs getting pulled into live
> image composes? can it be blacklisted or something?
It won't be problem only in case of live image composes, but in
requiring libmysqlclient.so.18 generally, because RPM simply chooses one
of the packages providing the same library. It is officially
un-deterministic (usually it is the shorter one), but we cannot depend
on it right now.
So to solve the live image composes issue for now I adjusted the major
soname number to libmysqlclient.so.1018. I know it doesn't solve all the
issues, though.
Can't we just remove MySQL-libs entirely? Or does MySQL-server require the
client library?
I wish FESCo had decided to just drop MySQL-server entirely, it would have
prevented all this fiasco!
Kevin Kofler