> > This I like. Having this not only for package dependencies but also for > > external dependencies would solve another pet peeve of mine... like header > > files being in slightly different locations on differrent systems (think > > /usr/include/lua.h vs. /usr/include/lua/lua.h) > > At least LR does that for us (it's /usr/include/lua5.1 on my Debian > box. The possibilities are endless ;))
my problem was with Tcl rather than lua, so it was actually tk/tcl.h vs. tcl.h, but I have also seen this with other libraries. This lua.h thing was just meant to be an example of how header files can lie at just slightly different positions on different systems. > But do look at > > http://www.luarocks.org/en/Platform-agnostic_external_dependencies don't help there. I agree that the "burden" of hinting where to find stuff would be better placed on the module packager. I know that a lot of people using lua and lua modules on linux or Mac OS don't know the first thing about compiling, header files and such stuff. To those people, if a module does not build out of the box, it means that the module does not build. Which is why I like the OR idea. It could solve a whole bunch of dependency related problems. Gunnar _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
