apis: west.manifest.Manifest.projects should not include the manifest itself
See original GitHub issueTrying to treat the manifest repository as an ordinary Project was doomed to failure; they’re simply too different. We should instead move the valid state that’s in ManifestProject today to Manifest attributes, removing MANIFEST_PROJECT_INDEX and the fact that projects[MANIFEST_PROJECT_INDEX] contains the manifest.
This will require a bit of thought into how west list
should behave, though. Maybe we need to resurrect west list --all
to include manifest project data like {path}
and {west_commands}
? And perhaps that should abort if you west list --all -f {url}
or try to access some other attribute that’s not defined for the manifest repository.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
West Manifests - Zephyr Project Documentation
Project and manifest repository histories don't have to move forwards or backwards together: P2 stays the same from A → B , as...
Read more >Web Application Manifest - W3C
This specification defines a JSON-based file format that provides developers with a centralized place to put metadata associated with a web ...
Read more >Create and configure apps with manifests - Slack API
Use our app manifest system to create, configure, and clone Slack apps with ease. ... No workspace should be without one! description: You...
Read more >How to add Golioth to an existing Zephyr project - Blog
Just list the Golioth Zephyr SDK as a module in your manifest file and the west tool will do the rest. Well, almost....
Read more >Project manifest parameters | Looker - Google Cloud
Model localization is not currently compatible with project import. Each project can have only one manifest file. The file must be named ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For sure, west list should continue to contain the manifest repository. It’s just the internal API I want to change.
⚠️ In case you start doing some work on this, remember that Zephyr modules uses
west list
to obtain a list of ALL projects, as those are candidates for being a Zephyr module: https://github.com/zephyrproject-rtos/zephyr/blob/51fc680ba225c2df5f3fca9064839b825a9c0511/scripts/zephyr_module.py#L177and in some cases the manifest project is ALSO a Zephyr module, and it would be bad to have
west
break backward compatibility to projects based on older Zephyr revisions. I would prefer a newwest
to also work if i checkout an old version of NCS, as example.