Cover Fedora 19's move from mysql to mariadb packages

[judge-red]

In their latest release, Fedora moved from mysql to mariadb. While the new packages "Provide" the old ones and Fedora's native tools handle this situation very well, Puppet's rpm provider unfortunately doesn't.

Therefore, if the OS is Fedora >= 19, the package names need to be s/mysql/mariadb/ now. Note that paths, etc. did not change.

[razorsedge]

While MariaDB is supposed to be a drop-in replacement for MySQL, there are already feature and compatibility differences. I wonder how much longer until MariaDB diverges significantly from MySQL that the requisite conditionals in this module make things unwieldy? Or should someone fork this MySQL module into one that deals only with MariaDB?

[apenney]

It's a good question and my gut instinct is "we'll fork it the first time we find some massive issue that can't easily be resolved with a simple conditional". It seems pretty clear to me that in another year or so you'll have to go out of your way to get 'MySQL' rather than MariaDB' so this module will almost certainly evolve with the decisions of the distributions in that regard.

Worst case we'll improve the ability for users to select MySQL or Mariadb and do the appropriate magic to make that happen to shield people from any weird compatibility differences.