mysql5 should be replaced_by mysql55, mysql56 or mariadb

[Craig Treleaven]

I would like to see a 'default' database:  my myth-related ports 
depend on a handful of other ports that now all default to MySQL 5.1 
via 'mysql5':

qt4-mac-mysql5-plugin
p5.1x-dbd-mysql
py2x-mysql

For Myth, MySQL 5.5 is well-supported on other platforms.  Initial 
reports say MariaDB is fine but it hasn't (yet) had the extensive 
usage that might shake out subtle incompatibilities.  As Bradley 
notes, several distributions are now, or will soon, make MariaDB the 
default so I expect any such problems will surface fairly soon and be 
dealt with.  So I guess I'd be OK with making it our default.

So, would we create a "virtual" port that points to MariaDB?

Question though:  what do we think the implications are of future 
MySQL/MariaDB versions?  Right now, I believe there are apps that are 
incompatible with specific versions.  If there is a MariaDB 5.6, do 
we expect that we'll have to maintain a MariaDB55 and create a new 
MariaDB56, and so on?  How quickly would we then change the virtual 
port to point to the new version?  (Bearing in mind that upgrading 
major versions sometimes requires a data migration.)  Won't we 
eventually be back in the position where the default is long 
out-of-date and yet there is resistance to changing it as the change 
requires manual intervention and creates risk?

This makes me think that we need a more-flexible system to specify 
preferred, acceptable and unacceptable database forks and versions. 
I'm not nearly smart enough to say how that ought to work.

Craig

At 9:21 AM -0700 8/3/13, Bradley Giesbrecht wrote:
>The mysql51, mysql55, mysql56, mariadb and percona ports do not 
>conflict so there are no common files, if thats what you meant.
>
>I would like MacPorts to have an [un]official default mysql port 
>that ports can depend on or the ports can provide variants or 
>subports for the other mysql's when desired.
>
>
>Regards,
>Bradley Giesbrecht (pixilla)
>
>
>On Aug 3, 2013, at 9:13 AM, Jeremy Lavergne wrote:
>
>>  Maria is a drop-in open source replacement for mysql. It also has 
>>many features that mysql has avoided adding (for future profit 
>>model?).
>>
>>  Mysql has already had some gaffs where they're hinting at closing 
>>up the source.
>>
>>
>>
>>  It's pretty clear mysql is on the way out, but it may not be there 
>>yet. Can you compare the installed files to find a common one we 
>>can check for a path:-style dependency?
>>
>>  On Aug 3, 2013, at 12:10 PM, Bradley Giesbrecht wrote:
>>
>>>  It appears many major distributions are switching from mysql to mariadb:
>>>
>>>  Redhat & Fedora:
>>> 
>>>http://linux.slashdot.org/story/13/06/14/1225257/red-hat-ditches-mysql-switches-to-mariadb
>>>  http://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB
>>>
>>>  Slackware and Arch Linux:
>>> 
>>>https://blog.mariadb.org/slackware-and-arch-linux-switch-to-mariadb-as-a-default/
>>>
>>>  OpenSUSE:
>>> 
>>>http://www.muktware.com/5148/opensuse-dumps-mysql-makes-mariadb-default-database
>>>
>>>
>>>
>>>  Those interested please vote or comment.
>>>
>>>
>>>  My vote:
>>>  +1 mariadb
>>>
>>>
>>>  Regards,
>>>  Bradley Giesbrecht (pixilla)
>>>
>>>  _______________________________________________
>>>  macports-users mailing list
>>>  macports-users at lists.macosforge.org
>>>  https://lists.macosforge.org/mailman/listinfo/macports-users
>
>_______________________________________________
>macports-dev mailing list
>macports-dev at lists.macosforge.org
>https://lists.macosforge.org/mailman/listinfo/macports-dev