linux/poky.git/bitbake/lib/bb/fetch2, branch 1.3_M1

lib/bb/fetch2: ignore remote URIs when doing file checksums

2012-05-30T16:23:32+00:00

Skip evaluating remote URIs when doing local file checksums, because we don't need to process them and doing so will trigger a parse failure if SRCREV is not fully specified. Whilst this is just delaying a check until runtime (when do_fetch runs for the recipe) we're only validating this here accidentally and if we did wish to check it during parsing it ought to be done explicitly. Fixes [YOCTO #2512] (Bitbake rev: 99feb77c2de707f2d825566cf48371c48f450e3e) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

lib/bb/fetch2: fix comments for verify_checksum

2012-05-25T10:15:12+00:00

This function no longer returns a value, it raises errors instead, so update the comments to reflect this. (Bitbake rev: 8b61b9584a8b00378f9fd8f165dbd65dcfd3c14e) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

replace os.popen with subprocess.Popen

2012-05-23T10:35:11+00:00

Replace os.popen with subprocess.Popen since the older function would fail (more or less) silently if the executed program cannot be found There is a bb.process.run() which will invoke the Popen to run command, use it for simplify the code. For the: p4file = os.popen("%s%s files %s" % (p4cmd, p4opt, depot)) ... for file in p4file: list = file.split() in bitbake/lib/bb/fetch2/perforce.py, it should be an error in the past, since it didn't use readline() to read the pipe, but directly used the split() for the pipe. Use the bb.process.run would fix the problem since bb.process.run will return strings. More info: http://docs.python.org/library/subprocess.html#subprocess-replacements [YOCTO #2075] (Bitbake rev: 8d6700255a6d4dda403c89b171a6d4a1883e5aae) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

replace os.system with subprocess.call

2012-05-23T10:35:11+00:00

Replace os.system with subprocess.call since the older function would fail (more or less) silently if the executed program cannot be found More info: http://docs.python.org/library/subprocess.html#subprocess-replacements [YOCTO #2075] (Bitbake rev: f5b3bf115dc1ffbfb241a49cec0fc3654cb71021) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: implement checksums for local files in SRC_URI

2012-05-23T10:35:04+00:00

Gathers a list of paths to have checksums calculated at parse time, and processes these when calculating task hashes. Checksums are cached with the file's current mtime. Thus, changing any local file in SRC_URI will now cause the do_fetch taskhash to change, thus forcing a rebuild. This change adds very roughly about an 8% increase in parse time (a few seconds) and maybe a few seconds during runqueue generation, so a fairly moderate performance hit. Note that since paths are resolved at parse time, this will not force a rebuild when files are introduced which would cause that resolved path to be different - for example, where a machine-specific version of a file was added without otherwise changing the recipe. This will need to be handled in a future update. Code to hook this into the signature generator was courtesy of Richard Purdie . Implements [YOCTO #2044]. (Bitbake rev: c993b7c457f8b7776e8a5dff253bfa0724bc2cae) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

fetch2: quote/unquote url paths

2012-05-22T13:56:16+00:00

This ensures we can handle things like %-encoded characters in the path portion of urls. (Bitbake rev: b1dbc24ebcc4e5100c32568c2c41fd982fb4bcce) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

fetch2: Also exclude urls containing wildcards from checksumming for now

2012-05-22T11:18:53+00:00

Without this change, bitbake will try and checksum a wildcard which will lead to fetch failures. (Bitbake rev: ac53b88be58b0bed21730c0b61a8fc8e801a2f1b) Signed-off-by: Richard Purdie

bb/fetch2/init.py: Don't try to compute checksums for directories

2012-05-21T08:59:00+00:00

In this way we avoid failing the build while trying to fetch local directories. [YOCTO #2475] (Bitbake rev: 39adb5741d9eee0879d3181be505400dffc60804) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

bitbake/fetch: Spell out which fetcher backends support and recommend checksums

2012-05-20T08:24:23+00:00

There were some hardcoded behaviours in the system for which backends support checksums verses which backends recommend them verses which don't recommend them. This moves the functionality into specific fetchers and then makes the general code generic. This cleans up the codebase and fixes some corner cases such as trying to checksum directories returned by the git fetcher. (Bitbake rev: ef6d268f7b8527541a7fb044cf95a973be4097f4) Signed-off-by: Richard Purdie

bitbake/fetch: If checksums are available, check them for any file, local or remote