diff options
author | Christopher Larson <chris_larson@mentor.com> | 2015-09-15 13:56:06 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-09-18 09:05:36 +0100 |
commit | 3a5e46b6ed483e43251da7e328b9299189997722 (patch) | |
tree | 579532935bca4c0c6765a21e294f7c59fb7a1591 /bitbake/lib/bb/data_smart.py | |
parent | 441f04ce97d12fd6b5f6cad9e23afe7080939092 (diff) | |
download | poky-3a5e46b6ed483e43251da7e328b9299189997722.tar.gz |
bitbake: bb.fetch2.{git, hg}: remove tarball if it needs updating
We were maintaining state in the form of ud.repochanged to determine whether
we need to write the tarball in the case where the tarball already exists, but
this state is maintained only in memory. If we need to update the git repo,
set ud.repochanged to True, and then are interrupted or killed, the tarball
will then be out of date.
Rather than maintaining this state, simply remove the out of date tarball when
we update the git repo, and it will be re-created with updated content in
build_mirror_data.
[YOCTO #6366]
(Bitbake rev: eaaa81393f181432c8586b17ade623f42c9fed2e)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/data_smart.py')
0 files changed, 0 insertions, 0 deletions