[MacPorts] #34618: swig: add swig-php53 and swig-php54 subports
#34618: swig: add swig-php53 and swig-php54 subports -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: kevin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: swig -------------------------------------+-------------------------------------- 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. -- Ticket URL: <https://trac.macports.org/ticket/34618> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34618: swig: add swig-php53 and swig-php54 subports ---------------------------+------------------------- Reporter: ryandesign@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: swig | ---------------------------+------------------------- Changes (by michaelld@…): * owner: kevin@… => michaelld@… -- Ticket URL: <https://trac.macports.org/ticket/34618#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#34618: swig: add swig-php53 and swig-php54 subports ---------------------------+------------------------- Reporter: ryandesign@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: swig | ---------------------------+------------------------- Comment (by michaelld@…): 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). -- Ticket URL: <https://trac.macports.org/ticket/34618#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#34618: swig: add swig-php53 and swig-php54 subports ---------------------------+------------------------- Reporter: ryandesign@… | Owner: michaelld@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: swig | ---------------------------+------------------------- Comment (by michaelld@…): 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 a description of what -does- make sense. -- Ticket URL: <https://trac.macports.org/ticket/34618#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#34618: swig: add swig-php53 and swig-php54 subports ---------------------------+------------------------- Reporter: ryandesign@… | Owner: michaelld@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: fixed | Keywords: Port: swig | ---------------------------+------------------------- Changes (by michaelld@…): * status: new => closed * resolution: => fixed Comment: Should be fixed in r120853. This revision works for me and should be OS version agnostic, so I'm closing this ticket as fixed. -- Ticket URL: <https://trac.macports.org/ticket/34618#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts