[MacPorts] #34507: make unified php ports
MacPorts
noreply at macports.org
Fri May 18 17:11:11 PDT 2012
#34507: make unified php ports
-------------------------------------+--------------------------------------
Reporter: ryandesign@… | Owner: ryandesign@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.1
Keywords: | Port: php5-gtk, php5-shindig, php5-spidermonkey, php5-igbinary, php5-uuid, php5-gearman, php5-timezonedb, php5-lzf, php5-rar, php5-stomp, php5-vld, php5-code-coverage, php5-file-iterator, php5-simpletest, php5-text-template, php5-timer, php5-token-stream, php5-unit, php5-unit-db, php5-unit-mock-objects, php5-unit-selenium, php5-suhosin
-------------------------------------+--------------------------------------
Now that we have the new unified php port (providing php53 and php54) and
php portgroup (providing php53-* and php54-* subports for extensions), we
need to convert all the php extension ports to the new unified format.
The bundled php extensions are already available as subports in the new
php port. I've also already converted most of the standalone extensions
maintained either by myself or by nobody (nomaintainer). If you're Cc'd on
this ticket, you are listed as the maintainer of one or more of the
remaining extensions (see below).
This ticket is meant to be informative, but you don't have to take any
action. I plan to convert the extensions myself, to get it done quickly
and consistently, and because I anticipate still needing to tweak the php
portgroup some and don't want any temporary deficiencies of the portgroup
to be a source of confusion.
Unlike the ongoing conversion to the unified python portgroup, since use
of the unified php portgroup requires using the new php binary ports as
well, and users are thus likely to want to switch from the old extensions
to the new ones all at once, the old ports will remain available and both
old and new ports should be kept updated and in sync until the entire
conversion is complete.
So, using Jeremy's php5-suhosin port as an example, I'll copy it to php-
suhosin, update it for the new php portgroup, and test it for php 5.3 and
5.4. If it builds as-is or if I can patch it for php 5.4 I'll do that; if
I can't (and for suhosin it so happens that I can't), then the port will
only be for php 5.3 and will need to wait for a new upstream version for
php 5.4 compatibility.
Once all extensions are converted to the new format, and all ports that
declare dependencies on them have been updated to have variants to select
which php to use, then the old php5-* ports will be marked as being
replaced_by their php53-* counterparts. After everyone has upgraded to
these new ports, the old php5-* ports will be deleted.
Here are the ports we're talking about:
'''kix.in:anant:'''
* php5-gtk
'''yahoo.com:bm55b:'''
* php5-shindig
'''ouarz.net:franck.cassedanne:'''
* php5-spidermonkey
'''pixilla:'''
* php5-igbinary
* php5-uuid
'''miwi:'''
* php5-timezonedb
'''freebsd.org:miwi:'''
* php5-lzf
* php5-rar
* php5-stomp
* php5-vld
'''medialize.de:rodney.rehm:'''
* php5-gearman
'''singingwolfboy:'''
* php5-code-coverage
* php5-file-iterator
* php5-simpletest
* php5-text-template
* php5-timer
* php5-token-stream
* php5-unit
* php5-unit-db
* php5-unit-mock-objects
* php5-unit-selenium
'''snc:'''
* php5-suhosin
--
Ticket URL: <https://trac.macports.org/ticket/34507>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list