Re: [PATCH 0/2] Move 'tag=' for a few SRC_URIs to SRCREV

[Saul Wold <sgw@linux.intel.com>]

On 10/08/2012 10:18 AM, Evade Flow wrote:
> Sending in response to:
>
>    - http://lists.yoctoproject.org/pipermail/yocto/2012-September/011802.html
>
> Building with BB_NO_NETWORK can fail if recipes specify 'tag=' in
> SRC_URI, since bitbake must contact the source repository to verify
> which hash the tag currently points to.  Since tags can, in principle,
> change, current best practice is to omit 'tag=' from SRC_URIs and
> instead specify the required revision hash in SRCREV.
>
> SHA hashes *cannot* change, so they should not need to be checked, in
> theory; however, bitbake currently has no mechanism for distinguishing
> between human-friendly tags like 'v2.1.2' and SHA-1 sums like
> 'fdb6c0402337d9607c7a39155088eaf033742752': both will result in a call
> to `git ls-remote` to verify the tag, which is problematic for
> BB_NO_NETWORK builds.
>
> The second part of this patch was, I think, already submitted, but not
> yet applied to master[?]:
>
>    - http://lists.yoctoproject.org/pipermail/yocto/2012-September/011949.html
>
>
> Evade Flow (2):
>    Move 'tag=' to SRCREV in btrfs-tools recipe
>    Move 'tag=' to SRCREV in mtd-utils recipe

In the future, please review the Commit & Patch Message Guidelines at
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

>
>   .../btrfs-tools/btrfs-tools_git.bb                 |    3 ++-
>   meta/recipes-devtools/mtd/mtd-utils_1.5.0.bb       |    3 ++-
>   2 files changed, 4 insertions(+), 2 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!