[MacPorts] #28529: swig language bindings need to be updated to the same version as swig
MacPorts
noreply at macports.org
Sat Feb 26 21:28:43 PST 2011
#28529: swig language bindings need to be updated to the same version as swig
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Reporter: ryandesign@… | Owner: jwa@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Resolution: fixed | Keywords:
Port: swig-allegro, swig-chicken, swig-clisp, swig-csharp, swig-gcj, swig-go, swig-guile, swig-java, swig-lua, swig-mzscheme, swig-ocaml, swig-octave, swig-perl, swig-php5, swig-pike, swig-python, swig-r, swig-ruby, swig-tcl |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Changes (by ryandesign@…):
* cc: apinstein@… (added)
Comment:
The swig and php5 packages are in identical situations. The swig language
bindings need to be updated to the same version as swig when the swig
version number increases, just as the bundled php5 extensions need to have
their versions updated to the same version as php5 when its version
increases. This is simply one of the responsibilities of maintaining swig
and php5.
I would hesitate to second-guess the developers of swig about how their
software works by changing their paths. Presumably there is a good reason
why the full version number is used.
--
Ticket URL: <https://trac.macports.org/ticket/28529#comment:10>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list