Re: [ANN] Kepler 1.1

["Fabio Mascarenhas" <mascarenhas@...>]

One workaround we use for the Kepler .exes is that they look for a
%EXENAME%.lua file in the same path where they are, if it's there they
use it for bootstrapping the Lua envinronment (setting LUA_PATH at the
least). But it's awkward as users have to create these files by hand,
so we just tell them to pass /scripts %LUAROCKS_BIN_DIR% to the
LuaRocks installer, less hassle. Maybe LuaRocks could create a
%EXENAME%.lua file with the appropriate bootstrapping when it copies
an .exe to scripts_dir?

--
Fabio Mascarenhas

On Wed, Jun 11, 2008 at 11:04 PM, Hisham <hisham.hm@gmail.com> wrote:
> On Wed, Jun 11, 2008 at 5:06 PM, Fabio Mascarenhas <mascarenhas@acm.org> wrote:
>> Hi, Ignacio,
>>
>> Where is your xavante.exe? Put it in the same place as lua5.1.exe
>> (probably c:\LuaRocks\0.5.2) and it should work. I am trying to
>> convince Hisham to make the LuaRocks binaries' dir and "scripts" dir
>> the same, so other executables can work without setting LUA_PATH too.
>
> The problem is that if scripts go inside the versioned LuaRocks dir,
> they go away when the user installs a new version and deletes the old
> one. For Lua command-line scripts, the scripts dir is designed to
> store .bat launchers which set the proper variables to make the
> package path work; installing .exes using LuaRocks is really a
> stretch, but I see it has its uses -- perhaps a similar approach is
> possible for .exes?
>
> -- Hisham
>