You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to integrate swipl into my build system. Here is the problem I encountered:
I have a main repository, on which I tinker with swipl-devel code. Then, I have a tool that clones that clone into another repository to perform builds. This allows me to decouple where I store and play with the code with builds on multiple SHAs.
Basically, when you "clone the clone", the remote repository of the clone of the clone is mapped to the clone and not to the github repository. As such, the relative paths for submodules are interpreted as relative to my filesystem and not as relative to the github setup. And it thus fails to clone the submodules.
The way I fix this is via a relatively arcane piece of trickery:
A better fix would be to make paths in your repository absolute for submodules in your .gitmodules file.
It would be cleaner anyway: as of now, it couples your repository with the implicit data of the hosting setup (in a non-explicit manner), which is counter to the original intent of git as a distributed system.
The text was updated successfully, but these errors were encountered:
Hi.
I've been trying to integrate swipl into my build system. Here is the problem I encountered:
I have a main repository, on which I tinker with swipl-devel code. Then, I have a tool that clones that clone into another repository to perform builds. This allows me to decouple where I store and play with the code with builds on multiple SHAs.
Basically, when you "clone the clone", the remote repository of the clone of the clone is mapped to the clone and not to the github repository. As such, the relative paths for submodules are interpreted as relative to my filesystem and not as relative to the github setup. And it thus fails to clone the submodules.
The way I fix this is via a relatively arcane piece of trickery:
This is awkward.
A better fix would be to make paths in your repository absolute for submodules in your
.gitmodules
file.It would be cleaner anyway: as of now, it couples your repository with the implicit data of the hosting setup (in a non-explicit manner), which is counter to the original intent of git as a distributed system.
The text was updated successfully, but these errors were encountered: