Closed rmartz closed 8 years ago
I'm a little bit concerned that we don't know the full picture. Another Github project seems to experience a similar issue but in that case it seems --recursive
fixes the problem, which is curious.
I'm also concerned that this might not be an OS X exclusive problem, though at the moment it definitely seems that way.
+1 agreed on those comments, not sure what else we can do at this point given time constraints though
Normally git uses relative paths for internal references. However, the stock version of git in OS X El Capitan, "2.7.4 (Apple Git-66)", will use absolute paths for submodule's gitdir property when the submodule is initialized at the same time as the parent repository is.
The workaround is to clone the repository in two steps, so that the submodule is initialized after the parent repository and given relative paths like Vagrant expects.