On Tue, Oct 26, 2010 at 7:19 PM, Hisham <[email protected]> wrote:

>
> This is weird, because the directory should be deleted when luarocks
> finishes. *And* the directory has the numeric process id in its name
> specifically to avoid those conflicts... I'll investigate this further
> when I get the time.
>

You're right. I did some more testing and it had nothing to do with the tmp
files. It just appeared like that because at the same time i was changing
the order in which the rocks are installed, strangely. Here are my latest
findings:

On a clean install (removing and reinstalling lua and luarocks directories)
it appear that
- lualogging before luadoc -> OK
- lualogging after luadoc -> conflict

After the clean/first install, leaving already installed luarocks, I notice
the following:
If I rerun the script, excluding lualogging and luadoc, all the rocks are
able to reinstall themselves without problems. Luarocks just detects that
the rocks are already in place and everything goes smoothly.

If I rerun the script, including installation of lualogging and/or luadoc
before the other rocks, then they conflict with each other or the rocks
after that. Giving similar errors to the ones I posted earlier.

So I expect there is something different about the lualogging and luadoc
rockspecs compared to the others. The relevant part of my script is:

LUAROCKS_BIN="${SANDBOX}/bin/luarocks"

# lualogging befor luadoc = OK
# luadoc before lualogging != OK

# lualogging
"$LUAROCKS_BIN" install lualogging
# luadoc
"$LUAROCKS_BIN" install luadoc

# penlight
"$LUAROCKS_BIN" install penlight
# install wsapi-xavante directly from trunk
"$LUAROCKS_BIN" install wsapi-xavante --from="
http://luarocks.org/repositories/rocks-scm";
# luaexpat
"$LUAROCKS_BIN" install luaexpat
# lunatest install from local rockspec since its not in any public
repository yet afaik.
"$LUAROCKS_BIN" install lunatest
--from="${ROOT}/external/lunatest-0.9.1-0.rockspec"


Hope this helps.

Thijs
_______________________________________________
Luarocks-developers mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers

Reply via email to