On Sep 26, 2012, at 14:59, [email protected] wrote:
> Revision: 98163
> http://trac.macports.org//changeset/98163
> Author: [email protected]
> Date: 2012-09-26 12:59:21 -0700 (Wed, 26 Sep 2012)
> Log Message:
> -----------
> php-midgard2: version bump to 12.09, make this a unified port, remove the
> unnecessary branch-specific port
>
> Modified Paths:
> --------------
> trunk/dports/php/php-midgard2/Portfile
>
> Added Paths:
> -----------
> trunk/dports/php/php-midgard2/
>
> Removed Paths:
> -------------
> trunk/dports/php/php5-midgard2/
php5-midgard2 should not be deleted yet. There are two possible strategies.
1. php5-midgard2 should be kept as-is and updated in sync with php-midgard2,
until such a time as we're ready to cut the cord and abandon the entire php5
world. This is the strategy I'm currently employing in all the other php
extension ports. All other ports that depend on php extension ports should be
updated to refer to the new unified php53/php54 ports, and once that's done,
then the old php5 ports can be marked as replaced_by the new php53 ports.
2. If there are no ports depending on php5-midgard2, and you do not believe any
of your users need to use any other php5 extensions as well, then php5-midgard2
could be immediately marked as replaced_by php53-midgard2.
One year after php5-midgard2 is replaced_by php53-midgard2, php5-midgard can
finally be deleted.
> Modified: trunk/dports/php/php-midgard2/Portfile
> +depends_lib port:midgard2-core
You should append to the dependencies, not overwrite them.
> +if {${name} != ${subport}} {
> + pre-configure {
> + system "cd ${worksrcpath} && phpize"
> + }
The php 1.1 portgroup runs phpize for you automatically.
>
> + configure.args-append --with-php-config=${php.config}
It also adds this configure argument for you.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
