From: Saul Wold <sgw@linux.intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sanity.bbclass: Add sanity check that TUNE_PKGARCH appears in PACKAGE_ARCHS
Date: Thu, 28 Jul 2011 20:07:55 -0700 [thread overview]
Message-ID: <4E32240B.6080606@linux.intel.com> (raw)
In-Reply-To: <C6AB40FE-3132-4788-A038-A7D877D52DE6@kernel.crashing.org>
On 07/28/2011 06:57 PM, Kumar Gala wrote:
>
> On Jul 28, 2011, at 7:41 PM, Saul Wold wrote:
>
>> On 07/28/2011 05:07 PM, Kumar Gala wrote:
>>> Its possible we get duplications if we explicity add TUNE_PKGARCH to
>>> PACKAGE_ARCHS so instead just add a sanity check to verify it.
>>>
>>> Signed-off-by: Kumar Gala<galak@kernel.crashing.org>
>>> ---
>>> meta/classes/sanity.bbclass | 10 +++++++++-
>>> 1 files changed, 9 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
>>> index b054146..999e15d 100644
>>> --- a/meta/classes/sanity.bbclass
>>> +++ b/meta/classes/sanity.bbclass
>>> @@ -375,8 +375,10 @@ def check_sanity(e):
>>> elif oeroot.find (' ') != -1:
>>> messages = messages + "Error, you have a space in your COREBASE directory path. Please move the installation to a directory which doesn't include a space."
>>>
>>> - # Check that we don't have duplicate entries in PACKAGE_ARCHS
>>> + # Check that we don't have duplicate entries in PACKAGE_ARCHS& that TUNE_PKGARCH is in PACKAGE_ARCHS
>>> pkgarchs = data.getVar('PACKAGE_ARCHS', e.data, True)
>>> + tunepkg = data.getVar('TUNE_PKGARCH', e.data, True)
>>> + tunefound = False
>>> seen = {}
>>> dups = []
>>>
>>> @@ -385,9 +387,15 @@ def check_sanity(e):
>>> dups.append(pa)
>>> else:
>>> seen[pa] = 1
>>> + if pa == tunepkg:
>>> + tunefound = True
>>> +
>>> if len(dups):
>>> messages = messages + "Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are listed more than once: %s" % " ".join(dups)
>>>
>> Kumar,
>>
>> Thanks for the patch, some questions.
>>
>> Is this correct, do you still want to report the error, if there is a dup?
>>
>> Would it not just be better to just drop the dup if it is the TUNE_PKGARCH?
>
> I wasn't sure how to drop the dup. :)
>
> If there is a way to uniq PACKAGE_ARCHS that would be fine
>
Would this be what your looking for, it "uniq"s only the tunepkg value.
- if seen.get(pa, 0) == 1:
+ if pa == tunepkg:
+ tunefound = True
+ if seen.get(pa, 0) == 1:
+ pkgarchs.remove(pa)
+ elif seen.get(pa, 0) == 1:
dups.append(pa)
else:
seen[pa] = 1
- if pa == tunepkg:
- tunefound = True
> - k
next prev parent reply other threads:[~2011-07-29 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 0:07 [PATCH] sanity.bbclass: Add sanity check that TUNE_PKGARCH appears in PACKAGE_ARCHS Kumar Gala
2011-07-29 0:41 ` Saul Wold
2011-07-29 1:57 ` Kumar Gala
2011-07-29 3:07 ` Saul Wold [this message]
2011-07-29 12:54 ` Kumar Gala
2011-08-02 17:29 ` Saul Wold
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=4E32240B.6080606@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=galak@kernel.crashing.org \
--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.