From: pieterg <pieterg@gmx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: AUTOREV and SRCPV
Date: Thu, 3 Jun 2010 11:22:17 +0200 [thread overview]
Message-ID: <201006031122.17227.pieterg@gmx.com> (raw)
In-Reply-To: <20100603082740.GL16035@jama>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On Thursday 03 June 2010 10:27:40 Martin Jansa wrote:
> A bit better would be to disable LOCALCOUNT_OVERRIDE only for recipes
> you want to be AUTOREV (then git clone will stop for recipes you don't
> care about even with BB_GIT_CLONE_FOR_SRCREV and after removing cache
> those LOCALCOUNT will stay 0 as it was before).
Check, this would be a good workaround for me at the moment.
Should we propose this patch? (see attachment, patch against bb 1.10)
Are the bitbake people reading along here?
Rgds, Pieter
[-- Attachment #2: 0001-allow-BB_LOCALCOUNT_OVERRIDE-to-be-defined-per-packa.patch --]
[-- Type: text/x-diff, Size: 1658 bytes --]
From 6265ab521627a38b9b0596149e31119b2073f5ba Mon Sep 17 00:00:00 2001
From: pieterg <pieterg@gmx.com>
Date: Thu, 3 Jun 2010 11:13:42 +0200
Subject: [PATCH] allow BB_LOCALCOUNT_OVERRIDE to be defined per package
---
lib/bb/fetch/__init__.py | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/lib/bb/fetch/__init__.py b/lib/bb/fetch/__init__.py
index 085f864..a586fda 100644
--- a/lib/bb/fetch/__init__.py
+++ b/lib/bb/fetch/__init__.py
@@ -695,7 +695,8 @@ class Fetch(object):
latest_rev = self._build_revision(url, ud, d)
last_rev = pd.getValue("BB_URI_LOCALCOUNT", key + "_rev")
- uselocalcount = bb.data.getVar("BB_LOCALCOUNT_OVERRIDE", d, True) or False
+ pn = bb.data.getVar("PN", d, True)
+ uselocalcount = bb.data.getVar("BB_LOCALCOUNT_OVERRIDE_pn-%s" % pn, d, True) or bb.data.getVar("BB_LOCALCOUNT_OVERRIDE", d, True) or False
count = None
if uselocalcount:
count = Fetch.localcount_internal_helper(ud, d)
@@ -705,9 +706,10 @@ class Fetch(object):
if last_rev == latest_rev:
return str(count + "+" + latest_rev)
- buildindex_provided = hasattr(self, "_sortable_buildindex")
- if buildindex_provided:
- count = self._sortable_buildindex(url, ud, d, latest_rev)
+ if not uselocalcount:
+ buildindex_provided = hasattr(self, "_sortable_buildindex")
+ if buildindex_provided:
+ count = self._sortable_buildindex(url, ud, d, latest_rev)
if count is None:
count = "0"
--
1.6.5.rc1.44.ga1675
next prev parent reply other threads:[~2010-06-03 9:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:51 AUTOREV and SRCPV pieterg
2010-06-03 4:35 ` Martin Jansa
2010-06-03 7:15 ` pieterg
2010-06-03 7:37 ` Martin Jansa
2010-06-03 8:02 ` pieterg
2010-06-03 8:27 ` Martin Jansa
2010-06-03 8:44 ` pieterg
2010-06-03 9:22 ` pieterg [this message]
2010-06-03 8:13 ` Phil Blundell
2010-06-03 8:30 ` Martin Jansa
2010-06-03 8:37 ` Phil Blundell
2010-06-03 8:46 ` Martin Jansa
2010-06-03 8:55 ` Phil Blundell
2010-06-03 16:35 ` Phil Blundell
2010-06-04 8:24 ` pieterg
2010-06-04 8:30 ` Phil Blundell
2010-06-04 8:44 ` pieterg
2010-06-04 11:03 ` Phil Blundell
2010-06-05 10:36 ` pieterg
2010-06-06 21:00 ` Phil Blundell
2010-06-07 0:13 ` Khem Raj
2010-06-08 10:09 ` Phil Blundell
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=201006031122.17227.pieterg@gmx.com \
--to=pieterg@gmx.com \
--cc=openembedded-devel@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.