On 05/09/14 8:52 AM, Giovanni Bechis wrote:
On 08/22/14 23:46, Stuart Henderson wrote:
On 2014/08/22 22:06, Stuart Henderson wrote:
On 2014/08/19 17:15, Brad Smith wrote:
Here is a diff to make attempt #2 at switching to MariaDB.
Going through the various Makefile's I noticed bmf had a typo
with its WANTLIB entry for MySQL.
It seems that files moved between -server (on mysql) and -client (on mariadb),
/usr/local/bin/msql2mysql (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/bin/mysql_find_rows (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/bin/mysql_waitpid (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/bin/mysqlaccess (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/man/cat1/msql2mysql.0 (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/man/cat1/mysql_find_rows.0 (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/man/cat1/mysql_waitpid.0 (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
/usr/local/man/cat1/mysqlaccess.0 (mysql-server-5.1.73p0v0 and
mariadb-client-10.0.13)
untested but perhaps adding "@conflict mysql-server-*" to mariadb/pkg/PLIST-main
will let this update automatically..
Not specific to mariadb (similar things happen with the standalone mytop)
but noticed this while testing:
This diff backported from upstream github repo
(https://github.com/CaptTofu/DBD-mysql) seems to fix it.
ok ? Comments ?
I don't see where that patch even came from in that repo. The repo you
pointed to is dead and AFAIK isn't used anymore.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
