swig: add swig-php53 and swig-php54 subports

[ryandesign (Ryan Carsten Schmidt)]

Currently there is a swig-php5 subport, which depends on path:bin/php:php5. The php5 and php5-devel ports are going away, and ${prefix}/bin/php will no longer be installed by a port. php5 and php5-devel are to be replaced by the new php53 and php54 subports, which install ${prefix}/bin/php53 and ${prefix}/bin/php54 respectively. I'm not sure how swig works, but I assume we should have new swig-php53 and swig-php54 ports, which let you build something for use with php53 and php54 respectively.

[cooljeanius (Eric Gallager)]

Cc Me!

[michaelld (Michael Dickens)]

The swig PHP subports need to be worked on: yes! I'll look into these, but I agree that it's probably adding swig-php5X and then making them conflict with each other; pick one and go with it. Could do this similarly for the gcj ones (gcj4X, to match +gcc4X).

[michaelld (Michael Dickens)]

So here's what I'm proposing doing:

1) Set swig-php5 as replaced_by swig-php.

2) Add +php5X variants to swig-php (similar to +gcc4X for gcj).

The above seems to make sense to me; and, they install correctly in my testing -- but, I do not otherwise use these ports so I cannot comment as to how well they work once installed. I'll push these changes once I have confirmation that they make sense; or, if they do not make sense, then a description of what -does- make sense.

[michaelld (Michael Dickens)]

Should be fixed in r120853. This revision works for me and should be OS version agnostic, so I'm closing this ticket as fixed.