It was thus said that the Great Geoff Leyland once stated: > > If I'm working on one module in the project, and then go and make > improvements to one of its dependencies, I pretty much always forget to do > a "luarocks make" in the dependency's directory before going back to the > first module, and so I don't get the changes until I go back and do that. > It's not a big deal, but it's something that "just worked" when the > project was a big messy bunch of files. > > Does anyone have any tricks for automating that, or improving the > situation? I thought about mucking with the install process so that it > hard-linked files rather than copied them, but there's got to be some > nicer solution than that, right?
Are you using some version control system? If so, you might want to write a script that does what you do that hooks into the VCS upon commit (I know you can do this with SVN and git). Or maybe a Makefile that does what you need to do. -spc ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
