summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/fetch2/hg.py
diff options
context:
space:
mode:
authorTyler Hall <tylerwhall@gmail.com>2012-12-19 18:26:50 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-18 12:50:12 +0000
commit0e408df69fd7a380d96501f13e81976eaea26fa4 (patch)
tree46490cc69f4a7851c56ed53a7fc414d519a3fa9e /bitbake/lib/bb/fetch2/hg.py
parentfe30cbc2cb0719092f19cba3b06a37e93260994c (diff)
downloadpoky-0e408df69fd7a380d96501f13e81976eaea26fa4.tar.gz
bitbake: fetch2: Sort file checksums by value, not path
Changing the path to a file could change the task hash even if the file still has the same checksum. This occurs when the task depends on multiple files and the sort order of their paths changes. Usually the sorting is consistent because layers tend to have the same relative paths, but this should take care of other configuations. The problem arose when using a .bbappend to add files to a recipe in another layer. If the layer is located alongside the other layers and their parent directory is moved, the hash does not change. However, moving the .bbappend layer outside of the common directory can change the path sort order and the task hash. (Bitbake rev: 22bd19d208f0251f5a1f9b98f3cac66181f3fc07) Signed-off-by: Tyler Hall <tylerwhall@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/fetch2/hg.py')
0 files changed, 0 insertions, 0 deletions