[MacPorts] #43431: Ports with a mysql5 variants and/or dependencies should switch to using mysql56 or possibly mariadb.
MacPorts
noreply at macports.org
Mon Apr 21 12:29:42 PDT 2014
#43431: Ports with a mysql5 variants and/or dependencies should switch to using
mysql56 or possibly mariadb.
--------------------------+--------------------------------
Reporter: pixilla@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: |
--------------------------+--------------------------------
Comment (by ryandesign@…):
Replying to [comment:2 dluke@…]:
> apr-util has other mysql variants - are we removing mysql5 variants now?
Is there a standard way we're deprecating them?
* mysql56 variants should be added where missing.
* mariadb and percona ports and variants should be renamed to be
versioned.
* mysql5 variants should be auto-upgraded to mysql51 variants ("`variant
mysql5 requires mysql51 description {Legacy compatibility variant} {}`"),
this way users using mysql5 databases only need to move their database to
a different directory to be able to continue using mysql51 (or, if just
checking if the variant is set, without defining the variant, correctly
upgrades users in that manner, then that's fine)
* mysql56 (or mariadb (or mariadb55 if we rename it)) should be the
default variant (which would apply for new installations, not upgrades)
* Alternately we could auto-upgrade mysql5 to mysql56 or mariadb (or
mariadb55 if we rename it), but then the user might have to do additional
steps other than just moving the files (e.g. running upgrade scripts). The
whole reason why we have versioned MySQL (and PostgreSQL and BerkeleyDB)
ports is so that users can decide when to upgrade to newer versions that
require such extra steps.
--
Ticket URL: <https://trac.macports.org/ticket/43431#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list