awesome

Welcome to awesome bug tracking system.
Tasklist

FS#983 - Lua 5.2 support

Attached to Project: awesome
Opened by Julien Danjou (jd) - Thursday, 29 March 2012, 13:43 GMT
Last edited by Uli Schlachter (psychon) - Friday, 11 April 2014, 09:16 GMT
Task Type Bug Report
Category Core
Status New
Assigned To No-one
Operating System All
Severity Medium
Priority High
Reported Version git/master
Due in Version 3.5.6
Due Date Undecided
Percent Complete 80%
Votes 1
Private No

Details

We should port awesome to Lua 5.2
This task depends upon

Comment by Rob Hoelz (hoelzro) - Thursday, 29 March 2012, 18:41 GMT
I think that Lua 5.2 is intended more as a version for new applications, rather than an upgrade path for existing ones. Converting the application to Lua 5.2 would require a good deal of work and little benefit; in fact, since 5.2 is still so young, very few modules have been ported to make use of it. Because of this, porting Awesome to Lua 5.2 would break nearly any rc.lua that uses external modules. Also, many Linux distributions are staying on Lua 5.1 for now; if you upgrade to 5.2, you either alienate users of distributions that don't ship 5.2, bring the burden of maintaining a Lua 5.2 package for these distributions on the Awesome community (assuming a third party 5.2 package doesn't already exist for those distributions), or require Awesome to include the Lua sources in its own source tree.
Comment by Uli Schlachter (psychon) - Thursday, 29 March 2012, 18:56 GMT
So you think that lua 5.1 will stick around forever? And so will 5.2, 5.3 and 5.4? Only horror awaits you at the end of that path.

Also, to make it clear: The goal of this bug is to make awesome work with lua 5.2 without breaking it with 5.1.
Comment by Rob Hoelz (hoelzro) - Thursday, 29 March 2012, 19:05 GMT
No, but it *is* still being maintained. I think that a move to 5.2 will have to happen someday, but I (personally) think it's too soon. I don't have a problem with a "port" to 5.2, so long as it doesn't appear in an official release for a while, just for the sake of not breaking users' configs left and right.
Comment by PaweĊ‚ Rumian (gorkypl) - Friday, 30 March 2012, 12:38 GMT
Hmm, I have always thought that "not breaking users' config" is against the awesome well-known policy of releases ;)
Comment by Alexander Yakushev (Alex.yakushev) - Wednesday, 23 May 2012, 22:17 GMT
Should it be on the 3.5 roadmap? I was hoping for 3.5 to appear more or less early, but tying it to lua 5.2 would require to wait for all major distributives to upgrade to new Lua. And it is not even in Arch yet.
Comment by Uli Schlachter (psychon) - Saturday, 23 June 2012, 06:56 GMT
The code changes for this should be done (thanks Asido!), but there is still some CMake-magic needed. CMake currently only looks for liblua.so and liblua51.so. So awesome uses lua 5.2 only on distros which call the library liblua.so. For example debian doesn't do this.
Comment by Uli Schlachter (psychon) - Wednesday, 26 March 2014, 13:42 GMT
There seems to be a new FindLua() in CMake:

http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindLua.cmake;hb=HEAD

Edit: Which will apparently be introduced in CMake 3.0. It's part of 3.0.0-rc2, but not in 2.8.12.2

Loading...