summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/runqueue.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2021-10-15 14:41:57 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-11-08 22:01:19 +0000
commit267eca35c1ac1e59a780ff433ad32018e294cc0f (patch)
tree2003f5d106602d04dc4fb8e6548b719405cc8d76 /bitbake/lib/bb/runqueue.py
parentbf411441f5368284ae6a6ac9707c689f48973083 (diff)
downloadpoky-267eca35c1ac1e59a780ff433ad32018e294cc0f.tar.gz
bitbake: fetch2/checksum/siggen: Fix taskhashes not tracking file directories
Currently if you have something like: SRC_URI = "file://foobar;subdir=${S}" and a file like: foobar/1/somefile and then move it to: foobar/2/somefile the task checksums don't reflect/notice this. The file-checksum fields encode two pieces of data, the file path and whether or not the file exists. Changing the code which uses these fields is problematic. We can however add a "/./" path element which means "include the bit after the marker in the checksum" which the path walking code can use to mark which bits of the path are visible to the fetcher. I'm not convinced this is great design but it does appear to work. (Bitbake rev: b4975d2ecf615ac4c240808fbc5a3f879a93846b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/runqueue.py')
0 files changed, 0 insertions, 0 deletions