On Mon, Oct 18, 2010 at 2:14 AM, Fabio Mascarenhas <[email protected]> wrote:
> Actually the original semantics relied on post_install being run after
> everything was in its final place. :-)
That makes sense - was certainly my understanding when reading the code.
Alexander would like a pre_install hook as well; I have an
experimental implementation in my clone repo. There the semantics
would be: run after the stage has been set, i.e. dependencies
resolved, archive expanded.
Perhaps a person wants to resolve external dependencies directly, etc.
Although we still need to strengthen that feature. In discussion
with Gunnar about the infamous moving-header-file problem in Linux,
this seemed like a workable idea
external_dependencies = {
FOO = {
header = 'foo.h;foo/foo.h'
}
}
where the items separated by semicolons would be checked in turn.
Look at
http://github.com/stevedonovan/luarocks/blob/e1dee6a3b3c3ba45b4b9de9d40c881b3e934c6fa/src/luarocks/deps.lua
around line 532 and 550 for the experiment. (this commit is a mess, sorry)
steve d.
_______________________________________________
Luarocks-developers mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
