Bug 973 - fetch2 no longer optional
Summary: fetch2 no longer optional
Status: RESOLVED NOTABUG
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-04-12 08:19 UTC by Paul Eggleton
Modified: 2011-05-06 14:17 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2011-04-12 08:19:56 UTC 
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')".
Comment 1 Richard Purdie 2011-04-12 11:08:31 UTC 
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.
Comment 2 Richard Purdie 2011-05-06 14:17:53 UTC 
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.