| Summary: |
Document SRCREV_* variable when multiple source controlled URLs are in SRC_URI |
| Product: |
[Documentation] Variables Glossary
|
Reporter: |
Quentin Schulz <foss+yocto> |
| Component: |
variables-glossary | Assignee: |
Adam Blank <adam.blank.g> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
adam.blank.g, antonin.godard, randy.macleod, simone.p.weiss
|
| Version: |
unspecified | |
|
| Target Milestone: |
5.3 | |
|
| Hardware: |
All | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
NEWCOMER |
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
SRC_URI = " \ git://some-git-repo;name=foo \ git://some-other-git-repo;name=bar \ " SRCREV_foo = "abcdef1234567890" SRCREV_bar = "1234567890abcdef" Note that SRCREV_FORMAT needs to be defined in that case. This is used in e.g. openembedded-core/recipes-kernel/linux/linux-yocto_5.4.bb SRCREV_machine_<override>= "yyy" SRCREV_meta = "xxx" SRCREV_FORMAT ?= "meta_machine" in openembedded-core/classes/kernel-yocto.bbclass bitbake/lib/bb/fetch2/__init__.py seems to be the code handling that logic. Documentation was expected in bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst apparently too, c.f. "We need to document ``AUTOREV`` and ``SRCREV_FORMAT`` here." so we could do that at the same time.