On Sun, Oct 17, 2010 at 10:14 PM, Fabio Mascarenhas <[email protected]> wrote: > On Sun, Oct 17, 2010 at 4:23 PM, Hisham <[email protected]> wrote: >> On Sat, Oct 16, 2010 at 2:51 PM, Alexander Gladysh <[email protected]> >> wrote: > >> I believe we added this feature (and I did so somewhat reluctantly) >> because some Kepler module needed to run some final setup task... but >> right now I can't find any rockspec using it in my cache of the >> repositories. Fabio, do you remember why we added this and if it is >> still needed? > > It was used by the Kepler package to do some initial setup, back in > LR1, probably the change from LR1 to LR2 broke the original semantics. > Currently none of my rocks use it, but hooks in general are a good > idea, I think. :-)
Hooks are a good way to define clear points of extensibility. My reluctance then was that I wanted to try to take the declarative power of rockspecs to the limit before resorting to hooks. I've seen (and perpetrated ;-) ) all sorts of hacks with hooks in GoboLinux recipes -- so far we've been able to keep rockspecs much cleaner in this regard. >> I'm asking this because moving it around like Alexander requested >> would change its overall semantics and I'm afraid it would break >> something. > > Actually the original semantics relied on post_install being run after > everything was in its final place. :-) All right, let's fix this then. -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
