From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] u-boot: set SRCREV to a git revision instead of a tag reference
Date: Tue, 21 Jun 2011 10:33:17 -0700 [thread overview]
Message-ID: <1308677603.2218.8.camel@scimitar> (raw)
In-Reply-To: <1046625816b98aaab44b810e2376ed3689a2af5f.1308677220.git.paul.eggleton@linux.intel.com>
On Tue, 2011-06-21 at 18:29 +0100, Paul Eggleton wrote:
> If we use a tag here then bitbake has to connect to the repository to find
> out the corresponding revision (so it can expand SRCPV which is part of PV,
> which amongst other things is needed to determine whether or not the
> package has to be rebuilt.) This occurs at parse time; on machines behind a
> firewall or with no network access this can be a problem.
>
> We wish to avoid unnecessary network accesses and network access in our
> default configuration during parse time is even worse. Substituting the
> git revision corresponding to the tag prevents bitbake from having to
> contact the remote repository in order to expand PV.
>
> Addresses [YOCTO #1186]
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Great work tracking this down! I wonder if it's worth mentioning in the
metadata that the revision corresponds to the tag?
Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> meta/recipes-bsp/uboot/u-boot_2011.03.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-bsp/uboot/u-boot_2011.03.bb b/meta/recipes-bsp/uboot/u-boot_2011.03.bb
> index 07f0609..25af69b 100644
> --- a/meta/recipes-bsp/uboot/u-boot_2011.03.bb
> +++ b/meta/recipes-bsp/uboot/u-boot_2011.03.bb
> @@ -12,9 +12,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb \
>
> FILESDIR = "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/u-boot-git/${MACHINE}"
>
> -SRCREV = "v2011.03"
> +SRCREV = "19b54a701811220221fc4d5089a2bb18892018ca"
> PV = "v2011.03+git${SRCPV}"
> -PR="r4"
> +PR = "r5"
>
> SRC_URI = "git://git.denx.de/u-boot.git;branch=master;protocol=git"
>
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-21 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 17:29 [PATCH 0/1] Fix for bitbake freeze due to git fetch during parse Paul Eggleton
2011-06-21 17:29 ` [PATCH 1/1] u-boot: set SRCREV to a git revision instead of a tag reference Paul Eggleton
2011-06-21 17:33 ` Joshua Lock [this message]
2011-06-21 17:49 ` Paul Eggleton
2011-06-21 17:34 ` Koen Kooi
2011-06-21 17:42 ` Paul Eggleton
2011-06-21 17:54 ` Koen Kooi
2011-06-21 17:59 ` Paul Eggleton
2011-06-21 18:06 ` Tom Rini
2011-06-21 17:33 ` [PATCH 0/1] Fix for bitbake freeze due to git fetch during parse Koen Kooi
2011-06-22 16:36 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308677603.2218.8.camel@scimitar \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.