Doesn't work with haxelib newrepo #64

Activity

1. ruby0x1 commented on Mar 30, 2017

   

   ruby0x1

   on Mar 30, 2017

   Member

   More actions

   If you can find documentation on the newrepo command I would take a look.
2. kevinresol commented on Mar 31, 2017

   

   kevinresol

   on Mar 31, 2017

   Last edited by kevinresol

   ContributorAuthor

   More actions

   Here it is, but it doesn't tell much.

   Basically the command itself does nothing more than creating a .haxelib folder at cwd.

   The really interesting part is that when haxelib runs, it will search for .haxelib folder in cwd and, if it exists, use that as the haxelib path. The same applies on the haxe compiler (which uses haxelib to resolve paths I believe).

   The tricky part is that the search for .haxelib only happens at cwd and will not "go up" the directory tree.
   So if flow runs haxelib-related things not at project root (where my .haxelib folder resides), it will be using the global haxelib path.

   You can see how I used this to check-in the haxelib dependencies of an app as submodules. So people doing a git clone --recursive will get the exact version of dependencies: https://github.com/haxe-react/haxe-react-native-sample