Hi,
coming by while looking at bugs dormant for a while.
@Robie / Lena - when reading the reference I think it outlines that conflict
well.
As far as i understand it:
We would - for example - in Ubuntu have a problem with an old
libmysqlclient that is installed along a new mysql-8 that brings newer
incompatible charsets to /usr/share/mysql.
The suggestion is to use (since being incompatible) versioned paths like
/usr/share/mysql-8.0 which is a path in which older client lib (or
anything else not bein 8.0) would never look.
I assume that is in our d/rules -DINSTALL_MYSQLSHAREDIR=share/mysql which could
as well be version specific avoiding the clash.
Maybe also worth a look while at it -DINSTALL_SUPPORTFILESDIR=share/mysql
The mentioned upstream defaults are in cmake/install_layout.cmake and
all are like ...mysql-${MYSQL_BASE_VERSION}...
Keeping the bug open and - unless I misunderstood - setting it to triaged.
One might have a new and deeper look now that the comment brings the case back
up for attention.
** Changed in: mysql-8.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
libmysqlclient21 use of /usr/share/mysql collides with mariadb-server-
core-10.3's use of the same directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1877504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
