| Summary: | Proposal to replace/rewrite gitsm | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Christopher Larson <kergoth> |
| Component: | bitbake | Assignee: | Mark Hatle <mark.hatle> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | mark.hatle, mark.jonas, poky.bs.watcher, poky.watcher, randy.macleod, rebecca.swee.fun.chang, sgw |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Christopher Larson
2017-07-24 22:08:52 UTC
I've created a thus-far working prototype of a rewritten gitsm that uses the bitbake fetcher for the submodules, and am currently testing it, mulling over how to address shallow support, and starting on thorough unit tests which don't all rely on network connectivity (we can construct the repositories we need on the fly, the way we do in the shallow unit tests). See https://gist.github.com/kergoth/9c163433c33cf883b21256459d743a98 for the current implementation. My team is affected by this issue as well. We are looking forward to a solution. :) The gitsm fetcher has been refactored and rewritten to address this, locking and other issues. The code changes went into the thud version (1.40). resolved |