[MacPorts] #45117: mythweb.27 @.27_1: depends on obsolete php5-mysql
MacPorts
noreply at macports.org
Wed Sep 24 08:01:36 PDT 2014
#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 |
--------------------------+--------------------------
Comment (by ctreleaven@…):
Replying to [comment:7 ryandesign@…]:
> 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.
Sorry Ryan, I was mainly just venting. I had to update from Perl 5.12 and
Python 2.4. I had hoped to hold off on these changes until Myth 0.28 was
released. The Myth release is, however, now months behind their original
timetable and MacPorts is 'pushing' me to make 'busy work' changes to a
functioning system. Myth is a pretty hairy beast and so lot's of people
let it run for years without touching it.
> 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 cannot locate any reports about MythWeb running successfully with PHP
5.6--5.4 is known to work OK. MythWeb is also going away. The project is
moving to an internal web server and modern replacement for MythWeb. Myth
0.28 will include a preliminary version of the new internal server. In
0.29, MythWeb is supposed to be gone.
I _could_ offer variants for:
* SQL: mysql51, mysql55, mariadb
* Perl: perl5.16, perl5.20
* Python: py26, py27
* PHP: php53, php54
The problem is support--I can't possibly test all the permutations. I
provide detailed, cookbook-style setup and configuration instructions via
the Myth wiki. Even so, I get lots of reported problems that boil down to
people missing a step. I haven't got the capacity to handle any more
complications.
> 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.
Thanks for pointing out that ticket. I know MythWeb is reported to work
with both nginx and lighthttpd but, as above, the package is going away.
If you want to continue this on the -dev or -users mailing lists, that's
fine with me...
--
Ticket URL: <https://trac.macports.org/ticket/45117#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list