[MacPorts] #45117: mythweb.27 @.27_1: depends on obsolete php5-mysql

[MacPorts]

#45117: mythweb.27 @.27_1: depends on obsolete php5-mysql
--------------------------+--------------------------
  Reporter:  alh_ports@…  |      Owner:  ctreleaven@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.3.1
Resolution:               |   Keywords:
      Port:  mythweb.27   |
--------------------------+--------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 Replying to [comment:3 ctreleaven@…]:
 > After years of moving at a measured pace, the MacPorts project blazed
 ahead just recently rendering Myth's Perl, Python, and PHP bindings
 obsolete.  Plus obsoleting the database.  My time is pretty tightly
 constrained at the moment but I will try to address the issue at hand
 ASAP.  I'm not a PHP guy; I'm not sure if differing versions of PHP in the
 backend v. MythWeb will cause issues.  Tested patches welcome!

 As far as I know there haven't been any major changes in the MacPorts Perl
 or Python ports lately (though discussions continue), however the PHP
 ports are mine, and I apologize for the lack of specific notification
 about finally replacing the old php5 ports, but note that the php53 ports
 which were designed to replace them have been available since May 2012
 already. I got tired of maintaining duplicate sets of PHP ports for years
 and decided that the recent release of the absolutely last ever version of
 PHP 5.3.x provided a good time to finally force this switch on those who
 had not yet done so.

 If possible (i.e. assuming mythweb does not specifically require only PHP
 5.4.x), please offer variants so the user can choose whether they want to
 use php53, php54, php55 or php56. I would suggest the default among those
 should be the latest stable version, currently php56.

 I see you added a dependency on the php54-apache2handler port. Is it
 absolutely necessary to run this under the PHP Apache module, or would the
 PHP CGI or FPM SAPI running under nginx or lighttpd or other web server
 also work (as it would for most PHP-based web sites)? If any PHP-capable
 web server would work, then you'll want to use the forthcoming ${php}-web
 metaport instead; keep an eye on #45008 for that.

-- 
Ticket URL: <https://trac.macports.org/ticket/45117#comment:7>
MacPorts <http://www.macports.org/>
Ports system for OS X