| Summary: | bitbake-setup: multiple remotes specified in config should create a single multi-remote repository | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Antonin Godard <antonin.godard> |
| Component: | bitbake | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alex.kanavin, paul, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 6.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
This spec with multiple remotes was designed before bitbake-setup, and particularly before the idea to use bitbake's git fetcher to handle git repos. Alas, the fetcher simply does not support this: you can't have multiple remotes all unpacked into the same directory. To be honest I'm also not sure if there's really a use case: if you want multiple remotes, it's typically when one of them is upstream, and another a private/company fork, so that you can do local development on it. For that, bitbake-setup has local sources and -L. There's also an upcoming patchset which simplifies this, and allows replacing the whole 'remotes' dictionary with a single 'uri':'where' property. I'll add myself to CC, but for now this needs further discussion, and is NEEDINFO/no assignee. Bulk move of 6.0 Medium bugs to 6.1. |
When specifying the following "sources" configuration: "sources": { "bitbake": { "git-remote": { "remotes": { "contrib": { "uri": "https://git.openembedded.org/bitbake-contrib" }, "origin": { "uri": "https://git.openembedded.org/bitbake" } }, "branch": "master", "rev": "master" } } At the moment, the last entry in "remotes" is cloned and the repository contains a single remote. One would probably expect a single repository to be created with multiple remotes? Up for discussion, maybe this property could be used differently.