| Summary: | list-packageconfig-flags.py: could not list skipped recipes | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Hongxu Jia <hongxu.jia> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | bluelightning, hongxu.jia, liezhi.yang, mark.hatle, meta.mr.watcher, meta.watcher, richard.purdie, sgw, yi.zhao |
| Version: | 1.5 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Hongxu Jia
2013-09-09 06:03:50 UTC
On the one hand, as far as an individual user using this command goes I don't think this is a big problem; the recipes are skipped because they aren't buildable for some reason, so the user would need to address that issue before they would be able to configure the recipe. We could report that the recipe has been skipped if that is a useful diagnostic for the user (bitbake-layers does this). On the other hand if we were to use this tool as a basis for producing some kind of reference documentation for general use, then it would be useful to be able to gather the packageconfig information from all recipes even if they are skipped in the current configuration. It may be tricky to make this work though. > On the other hand if we were to use this tool as a basis for producing some
> kind of reference documentation for general use, then it would be useful to
> be able to gather the packageconfig information from all recipes even if
> they are skipped in the current configuration. It may be tricky to make this
> work though.
Agree, this script is used to collect packageconfig from all recipes as many as possible. and not used to report the skipped issue.
Reading over this again, I just had a thought - SOURCE_MIRROR_FETCH (a rather poorly named variable) may be useful for the second case if used carefully. I don't think we'd want to always set it by default within list-packageconfig-flags.py, but it could be an option, or at least part of the documented procedure for generating packageconfig flag lists for all recipes. I think this is the defined behavior, it only lists available options. Closing as working as designed. |