Poky Project Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: a new problem with sstate
Date: Sun, 28 Nov 2010 15:12:30 -0700	[thread overview]
Message-ID: <4CF2D3CE.1010108@mentor.com> (raw)
In-Reply-To: <1290946854.27143.65.camel@rex>

On 11/28/2010 05:20 AM, Richard Purdie wrote:
> On Wed, 2010-11-17 at 07:31 -0700, Tom Rini wrote:
>> With old style packaged-staging we workaround this by doing:
>>
>> # We want to be certain that the scene is set for us only after it's set for
>> # our dependencies, to avoid problems with pstage package install order.
>> do_setscene[deptask] = "do_setscene"
>>
>> Can something similar be done for the sstate way of the world?
>
> Unfortunately not. sstate differs as the code tries to be clever about
> the dependencies and reverse walks the dependency tree. This means that
> if:
>
> A =>  B =>  C =>  D =>  E
>
> where "=>" means "depends on" then sstate will try and install a sstate
> package for A, then B, then C and *stop* once it finds a match.
>
> This fixes one of the annoyances of packaged-staging where if you're
> building an image and have all the ipks installed, it would still
> install the cross toolchain.

Er, so you're saying sstate has a 3 steps back limit?  Or am I just 
misunderstanding the example?  That would sound like other things are a 
bit hard to get done with sstate?  Or should stuff like bitbake 
virtual/kernel ; bitbake -c menuconfig virtual/kernel ; bitbake 
virtual/kernel (roughly...) still work?

-- 
Tom Rini
Mentor Graphics Corporation


  reply	other threads:[~2010-11-28 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 13:21 a new problem with sstate Tian, Kevin
2010-11-17 14:28 ` Joshua Lock
2010-11-17 14:31   ` Tom Rini
2010-11-18  5:15     ` Tian, Kevin
2010-11-18  6:40       ` Tian, Kevin
2010-11-28 12:20     ` Richard Purdie
2010-11-28 22:12       ` Tom Rini [this message]
2010-11-28 23:06         ` Richard Purdie
2010-11-28 23:21           ` Tom Rini
2010-11-29 13:03             ` Richard Purdie
2010-11-18  5:14   ` Tian, Kevin

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=4CF2D3CE.1010108@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=poky@yoctoproject.org \
    --cc=rpurdie@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox