Opened 5 years ago
Closed 4 years ago
#13213 closed Bugs (duplicate)
Relative path to submodules should point to boostorg instead of parent repo.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | To Be Determined | Component: | None |
| Version: | Boost 1.63.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
After forking super project 'boost' and trying to update modules git reports error: It expects sub-projects to be located in parent directory of forked repo. So to build correctly every single sub-project must be forked as well.
The relative path in .gitsubmodules should point to the /boostorg/* organization so sub projects could be updated from original location.
For more details please look at https://github.com/boostorg/boost/pull/33
Note:
See TracTickets
for help on using tickets.
Since it was also reported to GitHub, I'm closing this as dup (Trac is read-only now, all new issues should go to GitHub).
Note, the linked PR was closed w/o merging on Oct 26, 2017.