-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide full, readable and editable "condition" element directly in component and file element #279
Comments
NXP manifest schema: sdk_manifest_v3.14.txt |
Moving component dependencies directly into component description body is relatively easy to implement, however that will break backward and forward compatibility for several tools, in particular : |
Readability can be improved by applying the following rules when constructing conditions:
Here is an example of readable conditions:
|
Thanks @edriouk, your suggestions indeed improve the readability to a certain extent. |
In existing pdsc, the dependencies of components are specified through "condition" mechanism. On component level, just a condition refer id is provided, the detailed definitions of the condition are defined in "conditions" element. If user needs to know details of one component dependency, he needs to search up to down, down to up, many times in the "conditions" to figure out the whole picture which is quite inconvenient. When he/she tries to update it, sometimes it is possible. Here is snap of existing NXP DFP conditions:
Suggested way to improve:
In this way, users can directly get full picture of the dependencies at the first glance with the most addressed component dependencies and without making the conditions too long and messy with too many hardware data.
Here is one simple example:
The same way applies to "files" element.
We believe that an human easily readable and editable pdsc files can better populate OCP solution especially in directly github repo daily development usage (not ready packs way)
GitHub repository as pack source
The text was updated successfully, but these errors were encountered: