Changes between Initial Version and Version 1 of Ticket #47290, comment 4


Ignore:
Timestamp:
Apr 14, 2015, 2:31:12 PM (9 years ago)
Author:
sk-public@…
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #47290, comment 4

    initial v1  
    11I uploaded digikam-mysql-2015-04-14.diff​, with mysql51_external, mysql55_external, mysql56_external, and mariadb_external variants, all of which enable support for external MySQL databases (as opposed to the default builtin SQLite). I've tested by building with the mysql56_external variant.
    22
    3 The patch also renames the mysql_check variant to mysql_internal, which better describes what that variant does (allow use of an internal MySQL database), and distinguishes it from the _external variants. However, I don't use that capability. I'm not even sure why it's necessary -- I built it by accident because I thought it might re-enable support for external MySQL databases.  It doesn't. I think it should be renamed to mysql_internal to prevent that confusion.  I did changed it to look for bin/mysql_config instead of mysql_config5. The former is created by port select --set mysql mysql5_, I don't think anything provides mysql_config5.
     3The patch also renames the mysql_check variant to mysql_internal, which better describes what it does (support using an internal MySQL database instead of SQLite), and distinguishes it from the mysql5X_external variants. I don't use this capability -- I'm not even sure why it's useful. I built it by accident because I thought it might re-enable support for external MySQL databases.  It doesn't. I think it should be renamed to mysql_internal to prevent that confusion.  I did change it to look for bin/mysql_config instead of mysql_config5. The former is created by port select --set mysql mysql5X, I don't think anything provides mysql_config5.