[bitbake-devel] [PATCHv2] bb.fetch2.{git, hg}: remove tarball if it needs updating

[Christopher Larson]

On Tue, Sep 15, 2015 at 2:23 PM, Christopher Larson <kergoth at gmail.com>
wrote:

> From: Christopher Larson <chris_larson at mentor.com>
>
> 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]
>
> Signed-off-by: Christopher Larson <chris_larson at mentor.com>


Ignore the v2, only removing it when write_tarballs is set could be
problematic if the repo is updated with write_tarballs not set, then it's
set afterward.
-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20150915/207bf2f3/attachment-0002.html>