From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/1] packagehistory improvement
Date: Tue, 22 Nov 2011 17:32:56 +0000 [thread overview]
Message-ID: <2298086.Af8fDfZKZy@helios> (raw)
In-Reply-To: <503E71C5-C1CA-4A51-82EF-C52CBC2E43C5@dominion.thruhere.net>
On Tuesday 22 November 2011 18:25:25 Koen Kooi wrote:
> Does it still suffer from the bug where it will break if you change machine
> and something goes backward in PV (e.g. gcc 4.6 is used on arm, but 4.5 on
> ppc)?
If the package in question is not tied to the machine or the arch that was
changed, yes it will still cause do_package to fail. I'd be happy to address
this, but my question would be, how do we tell the difference between a
legitimate version pinning and when something has gone wrong?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-22 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:52 [RFC PATCH 0/1] packagehistory improvement Paul Eggleton
2011-11-22 14:52 ` [RFC PATCH 1/1] classes/packagehistory: fix and extend Paul Eggleton
2011-11-22 17:25 ` [RFC PATCH 0/1] packagehistory improvement Koen Kooi
2011-11-22 17:32 ` Paul Eggleton [this message]
2011-11-23 13:24 ` Paul Eggleton
2011-11-23 13:31 ` Koen Kooi
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=2298086.Af8fDfZKZy@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox