| Summary: | fetch2 no longer optional | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Paul Eggleton <bluelightning> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher, sgw |
| Version: | 1.0 | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
fetch2 is required, that isn't an issue. Upstream bitbake doesn't have the hardcoding you refer to, we did that in Poky when fetch2 was under development. We should be able to match upstream bitbake now. As far as I can see we force the use of fetch2 in the environment script which is fine. Its not meant to be optional. That code does have effect in bitbake upstream and poky needs to sync with that which will happen naturally over time. |
It seems fetch2 is no longer optional. Either this is a problem (and I don't think it necessarily is), or we should remove BBFETCH2 and related logic in the bitbake wrapper. Currently BBFETCH2 has no effect in any case (the code that reads it says something like "if True or os.environ('BBFETCH2')".