At the risk of maybe reopening an old discussion, I wonder:
How would you feel about installing rocks locally within each project, so
that different projects' dependencies can't interfere, and each project
self-contains all of its dependencies?
I mean: each project should contain its own rocks_tree, and it should be
the default tree for installs. When loading rocks, the tree should be
sought in the current directory, and if not found, one directory up towards
the root, and so on.
For common rocks, that are more like commands or tools on their own than
like libraries you would require in a project, a global rocks_tree could be
useful, apart from the project-trees. But global installations should be
special cases.
To prevent possible confusion: the current global (all users) and local
(current user) locations are both global in this respect. By local I mean
local to a project, so within the project directory.
Cheers.
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete
for recognition, cash, and the chance to get your game on Steam.
$5K grand prize plus 10 genre and skill prizes. Submit your demo
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
