Changes between Initial Version and Version 1 of Ticket #46621, comment 17


Ignore:
Timestamp:
Sep 16, 2015, 6:45:26 AM (9 years ago)
Author:
dbevans (David B. Evans)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #46621, comment 17

    initial v1  
    1 Although I think updating lua to version 5.3.0 was done without much thought to what might break,  trying to support multiple versions of lua is adding complexity that really isn't called for as long as backwards compatibility support for both lua 5.1 and 5.2 is enable in the 5.3 build.  While there are a few API items from 5.2 that were dropped from 5.3, the changes are minimal particularly for apps that are 5.2 compatible already and are easily handled as in the case of luaL_checkint as mojca has indicated.  See the [http://www.lua.org/manual/5.3/manual.html#8 5.3 manual] for details of known incompatibilities with 5.2.  I don't think 5.1 and earlier is much of an issue as most upstream developers now support 5.2 and several have updated releases for 5.3 where necessary. I think the current lua50 port could be removed as there are no ports that depend on it and lua51 only has one, borwars which hasn't seen much development in a long time and its compatibility problems have to do with 5.1 vs 5.2. So the main issue to my mind is 5.2 verses 5.3.
     1Although I think updating lua to version 5.3.0 was done without much thought to what might break,  trying to support multiple versions of lua is adding complexity that really isn't called for as long as backwards compatibility support for both lua 5.1 and 5.2 is enabled in the 5.3 build (as it is now).  While there are a few API items from 5.2 that were dropped from 5.3, the changes are minimal particularly for apps that are 5.2 compatible already and are easily handled as in the case of luaL_checkint as mojca has indicated.  See the [http://www.lua.org/manual/5.3/manual.html#8 5.3 manual] for details of known incompatibilities with 5.2.  I don't think 5.1 and earlier is much of an issue as most upstream developers now support 5.2 and several have updated releases for 5.3 where necessary. I think the current lua50 port could be removed as there are no ports that depend on it and lua51 only has one, borwars which hasn't seen much development in a long time and its compatibility problems have to do with 5.1 vs 5.2. So the main issue to my mind is 5.2 verses 5.3.
    22
    33Finally, note that lua extension modules need to be installed in a given lua's search path to be useful.  Typically this is ${prefix}/lib/lua/${lua_version} for binary modules and ${prefix}/share/lua/${lua_version} for lua modules.  So to fully support more than one version of lua, we would need to address multiple versions of these as well.  Do we really want to get into another multiple version can of worms? I suggest we do as we have decided to do with perl and just support the latest stable version.
    44
    5 I suggest before proliferating multiple lua versios, we make a list of ports that seem to be broken with 5.3 to understand the magnitude of the problem and then see if we can understand what the various issues are.  I would much rather work with the upstream developers to fix any 5.3 incompatibilities than try and support multiple lua versions. In short, I favor moving forward rather than standing still or moving backward.
     5I suggest before proliferating multiple lua versions, we make a list of ports that seem to be broken with 5.3 to understand the magnitude of the problem and then see if we can understand what the various issues are.  I would much rather work with the upstream developers to fix any 5.3 incompatibilities than try and support multiple lua versions. In short, I favor moving forward rather than standing still or moving backward.
    66
    7 As you are probably aware, the upgrade to 5.3 broke libquvi and libquvi-scripts which in turn broke playlist parsing in the GNOME video player, totem. This is now fixed to work with lua 5.3. Although libquvi and friends claim to only be 5.1 compatible, it took very few changes to get it all working again.
     7As you are probably aware, the upgrade to 5.3 broke libquvi and libquvi-scripts which in turn broke playlist parsing in the GNOME video player, totem. This is now fixed to work with lua 5.3. Although libquvi and friends claim to only be 5.1 compatible, it took very few changes to get it all working again.  Basically enabling 5.1 compatibility in 5.3, rebuilding libquvi against the resulting liblua and making sure the necessary lua modules install in the 5.3 search path.
    88