lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Since LfW was an alpha, and it's just been on this Lua list & LuaForge
( it's had limited exposure) should be enough to put a Note saying
'Uninstall last Alpha before installing Beta'. and not change current
directory structure for libraries.

How many Apps with Lua embedded wouldn't just hardcode their paths to
guarantee they can't be interfered with? I'd guess most. But for
future compatibility need to fix these kind of 'playing nice together'


On Fri, Jun 13, 2008 at 9:15 AM, RJP Computing <> wrote:
> On Fri, Jun 13, 2008 at 9:08 AM, Andrew Wilson <> wrote:
>> Yes, need to fix Lfw LUA_PATH as you described Ryan. But I think just
>> changing to lua isn't going to help any other apps. The idea of having
>> Lua apps  & components not break each other by design is critical. So
>> I think that David's inverting logic for paths by allowing  "';; to
>> optionally be specified in luaconf.h (by default at the end of the
>> search path) and let this represent the search path defined in the
>> global environment variable.' should resolve the problem completely
>> for next version of Lua. But for next release of Lfw need to put ";;"
>> in front of path names.
> Do we need to change the directory name for the Lua libraries?
> I added that to the installer, now since this is beta LfW people might need
> to manually remove the current path, before installing this update. I can
> only add to the environment, and make sure I don't duplicate entries. I
> can't delete them.
> --
> Regards,
> Ryan
> RJP Computing