From: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] base.bbclass: add SRCREV to do_fetch() hash
Date: Mon, 29 Sep 2014 16:52:14 +0200 [thread overview]
Message-ID: <201722111.zmNURQEFnj@comp-006-thk> (raw)
In-Reply-To: <1412001614-15126-1-git-send-email-ross.burton@intel.com>
On Monday 29 of September 2014 15:40:14 Ross Burton wrote:
> Without this changing just the SRCREV won't re-fetch unless you embed the
> SRCREV into PV.
So a trick like this will not be needed anymore to automatically rebuild
whenever sources in SCM change?
SRCREV = "${AUTOREV}"
PVBASE := "${PV}"
PV = "${PVBASE}.${SRCPV}"
>
> The downside here is that every hash changes, so this causes a full rebuild.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/classes/base.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index c0d61fe..ff8c633 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -97,6 +97,7 @@ PATH_prepend = "${@extra_path_elements(d)}"
> addtask fetch
> do_fetch[dirs] = "${DL_DIR}"
> do_fetch[file-checksums] = "${@bb.fetch.get_checksum_file_list(d)}"
> +do_fetch[vardeps] += "SRCREV"
> python base_do_fetch() {
>
> src_uri = (d.getVar('SRC_URI', True) or "").split()
--
Maciej Borzęcki
Senior Software Engineer Open-RnD Sp. z o.o.
www.open-rnd.pl, Facebook, Twitter
mobile: +48 telefon, fax: +48 42 657 9079
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged or
confidential information and is sent solely for the attention and use of the
intended addressee(s). If you are not an intended addressee, you may neither
use this message nor copy or deliver it to anyone. In such case, you should
immediately destroy this message and kindly notify the sender by reply email.
Thank you.
next prev parent reply other threads:[~2014-09-29 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 14:40 [PATCH] base.bbclass: add SRCREV to do_fetch() hash Ross Burton
2014-09-29 14:52 ` Maciej Borzecki [this message]
2014-09-29 14:56 ` Burton, Ross
2014-09-29 17:14 ` Martin Jansa
2014-09-29 17:23 ` Burton, Ross
2014-09-29 18:48 ` Martin Jansa
2014-10-07 18:26 ` Khem Raj
2014-10-07 18:26 ` Khem Raj
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=201722111.zmNURQEFnj@comp-006-thk \
--to=maciej.borzecki@open-rnd.pl \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.