I want to install a program using LuaRocks's built-in installer if possible (currently I have a GNU autotools build system).
One thing that I currently use autoconf/automake to do is to patch the path of where some files belonging to my package are into the executable script. I see that I can require "luarocks.cfg" to get some information about how luarocks is configured, but it's not obvious that this is guaranteed to work (it seems to be undocumented), nor that I can get the information I want (where my particular rock is installed). In case there's another way around my difficulty, here's the precise problem I'm trying to solve: my program provides wrappers for common commands, like du, df, ps &c. which colour their output. These wrappers are installed in a directory which the user can add to PATH for interactive sessions (no point using them non-interactively). It doesn't matter where this directory is, but the user should be able to discover what it is (currently it is patched into the man page at install time). More importantly, each wrapper script invokes the main program, which then re-invokes the correct command, having first filtered the script directory out of PATH. To do this, it seems to be necessary to know what that directory is! Again, currently autotools patches this path into the script, but it would be nice to do without. Suggestions? -- http://rrt.sc3d.org ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
