Open mbolivar-nordic opened 1 year ago
Discussion among @carlescufi @tejlmand @aescolar @mbolivar-nordic :
Fact that this cannot be overridden in an importing manifest is a serious problem. E.g. in NCS we could not write a manifest that imports zephyr and makes bsim active by default.
Potential way forward, not vetted, just an RFC
manifest:
projects:
- name: zephyr
import:
name-allowlist:
- bsim
- ...
activate:
- bsim
This issue tracks a potential extension to the manifest schema. It is not a proposal at this point, just a placeholder for discussion.
Proposed syntax:
Proposed semantics:
false
, no behavior changestrue
, new behavior applies to whether project is active or inactiveThe new behavior that applies if and only if the key is
true
is:manifest.project-filter
applies to the project, it decides whether the project is active or inactive;inactive-by-default
has no effect in this caseThis applies regardless of where the project is defined in the import hierarchy.
Concerns:
west init
+west update
will not result in a manifest that can be resolved