Re: PATCH: Lua5.1-work3 loadlib cleanups

[Adrián Pérez <copylight@...>]

El 08/12/2004, a las 9:39, Asko Kauppi escribió:

> But about the local/lib vs. local/share, still.. *nagging*  . [...] 
> And I'd personally prefer to keep a module's wrapper (.lua) and the 
> module itself (.so) as close to each other in the filesystem as 
> possible.

After thinkign a bit about that, there's a tricky situation.  A .lua 
script with a shebang in the first line (like "#! /usr/bin/lua) and 
marked as executable: does it continue to be "inert text" or is it 
"alive code"?? In my opinion it's alive, as it contains code (even 
without the shebang and not having execute permission it would be code, 
indeed).

And, if scripts are "alive code" thay should go into "*/lib" instead of 
"*/share", isn't it? In LuaCheia we use somethings like 
"/usr/local/lib/luacheia5" to store both binary modules and Lua scripts 
because it's easy to do that way with automake -- but now I think it's 
the better approach.

-ap

Attachment: PGP.sig
Description: Mensaje firmado digitalmente