RE: Makefile vs LUA_PATH inconsistency

[Thijs Schreijer <thijs@...>]

> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On
> Behalf Of Andrew Starks
> Sent: dinsdag 20 mei 2014 17:24
> To: Lua mailing list
> Subject: Re: Makefile vs LUA_PATH inconsistency
> 
> 
> On Tue, May 20, 2014 at 5:07 AM, Philipp Janda <siffiejoe@gmx.net> wrote:
> Someone mentioned MS had rules for the locations of modules, scripts, etc.
> I'd rather see those locations added on Windows (or use the paths from LfW
> or LuaDist), so that you can write an installer for Lua that fits well with
> the rest of the Windows ecosystem (although an installer could just as
> easily set environment variables and/or use the paths relative to the
> executable).

Unfortunately, like you mentioned yourself, there is no "rest of the windows ecosystem". LfW is end of life, LuaDist set its own rules, and LuaRocks uses the same structure as 'make install' does.

> 
> I mentioned this. If one were to be installing Lua for desktop use, then
> modules should be stored in a `%APPDATA%`\lua folder and a second search
> tree rooted in `%USERPROFILE%\\lua`. This [1] is a good summary of all of
> the relevant variables and what they're for. But I understand if this is
> deemed beyond the scope of intent for the main tar ball.
> 
> If Lua is a sandbox for applications, then the current configuration is
> ideal, provided there is a decent VS project. Right now, this [2] is as good
> as it gets.
> 
> Oh, and [3]. :)
> 
> -Andrew
> 
> [1] http://technet.microsoft.com/en-us/library/cc749104(v=ws.10).aspx
> 
> [2] http://techneilogy.blogspot.com/2012/02/compiling-lua-with-visual-
> studio-2010.html
> 
> [3] Also, I think a further discussion about practical methods to handle
> writing modules for multiple 5.X versions of Lua and also, secondarily,
> using them. In particular, I still like the idea that the actual search path
> in Lua 5.3 might support specific version trees, with fallbacks to general
> "lua" trees. My suggestion was "user_lua/5.3->user_lua->lua/5.3->user_lua-
> >cur_dir/5.3->cur_dir". This would make it possible to write modules that
> could optionally use different files as a way to manage differences, which
> might be more important in 5.3 than it was for 5.1-5.2.

The 'make install' structure perfectly well supports this, you only need to version the lua.exe and luac.exe.