#46621: Update: lua 5.3.0 -----------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: lua | -----------------------------+-------------------------------- Comment (by ryandesign@…): lua is one of those languages that seems to break backward compatibility with each version. Not every lua-using program is affected, but it seems like some always are. This is exactly the kind of software that should have multiple simultaneously-installable (sub)ports so the user (or the other program) using lua can choose which version they want. It's the same reason why we offer multiple versions of python, ruby, php, clang, gcc. Dave, I am definitely in favor of "moving forward" as you said above, just that I have a different definition of "moving forward" than you do. To me, "moving forward" is providing and maintaining the multiple versioned ports of lua, so that even old software can be built with lua support. Removing old lua ports would be moving backward, to me, in that it would break ports that require those old versions of lua. Even if there aren't many ports in MacPorts today that require old versions of lua, it's possible new ports will be added that require old lua, or that some of the ports that currently declare a dependency on just "lua" actually require an older version and have just not been tested with newer versions yet. (One example I'm currently working on: #39074.) -- Ticket URL: <https://trac.macports.org/ticket/46621#comment:20> MacPorts <https://www.macports.org/> Ports system for OS X