All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky <poky@yoctoproject.org>
Subject: Re: Master stability update
Date: Wed, 26 Jan 2011 11:42:04 +0000	[thread overview]
Message-ID: <1296042124.27814.2557.camel@rex> (raw)
In-Reply-To: <4D3F9A27.3050409@windriver.com>

On Tue, 2011-01-25 at 21:51 -0600, Mark Hatle wrote:
> On 1/25/11 9:05 PM, Tian, Kevin wrote:
> >> From: Tian, Kevin
> > After a quick check, I guess this is not a problem. for example perl.do_configure
> > changes checksum due to $MACHINE in dependency variables as Dongxiao said.
> > Once perl is not reusable, at least ~10 recieps (libzypp, libtool, rpm, ...) are not
> > reusable too because perl is in their task dependency chain.
> > 
> > I didn't check all the differences yet, but overall feeling is that this should be OK
> > as Dongxiao mentioned there're several obvious MACHINE related recipes. I'll
> > leave to Dongxiao for final confirmation. :-)
> 
> It might be nice (if not a bit dangerous) to be able to say "I want perl version
> X.Y.Z.  I don't really care about the checksum, as long as the version matches..."
> 
> In the case of perl, this is likely to do exactly what we want/need.  In the
> case of other packages (particularly libraries) this could cause serious problems...

Adding "perl" to BB_HASHTASK_WHITELIST would do exactly what you
describe so its at least possible although it doesn't cover a version
specific match which would probably be better as part of DEPENDS
handling.

Stopping it being machine specific is the first thing that needs fixing
though (I have a patch I'm testing for that one).

Cheers,

Richard



  reply	other threads:[~2011-01-26 11:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 22:07 Master stability update Richard Purdie
2011-01-26  2:45 ` Xu, Dongxiao
2011-01-26  2:52   ` Tian, Kevin
2011-01-26  3:05     ` Tian, Kevin
2011-01-26  3:51       ` Mark Hatle
2011-01-26 11:42         ` Richard Purdie [this message]
2011-01-26  3:52       ` Xu, Dongxiao
2011-01-26  3:55         ` Xu, Dongxiao
2011-01-26 10:01         ` Richard Purdie
2011-01-26 10:31           ` Tian, Kevin
2011-01-26  6:58 ` Saul Wold
2011-01-26  7:01   ` Xu, Dongxiao
2011-01-27 12:45 ` Koen Kooi
2011-01-27 15:06   ` Richard Purdie
2011-01-27 15:35     ` Koen Kooi
2011-01-27 17:01       ` Koen Kooi
2011-01-27 21:45       ` Richard Purdie
2011-01-27 23:33         ` Koen Kooi
2011-01-28  7:56         ` Koen Kooi
2011-01-28 16:59           ` Richard Purdie
2011-01-28 17:42             ` 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=1296042124.27814.2557.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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.