All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Proposed roadmap and design for Hob improvement
Date: Tue, 25 Oct 2011 11:09:04 -0700	[thread overview]
Message-ID: <4EA6FB40.7050600@linux.intel.com> (raw)
In-Reply-To: <CAEsOVNdfJ_VRRNVRGNf3C7ziBdn4uaa3hNUk5hSAQnj9zimkYQ@mail.gmail.com>



On 25/10/11 09:08, McClintock Matthew-B29882 wrote:
> On Sun, Oct 23, 2011 at 10:12 PM, Yu, Ke <ke.yu@intel.com> wrote:
>>> Seems like with the build packages and build image steps separated you could
>>> skip the build step completly for most packages if we ship or host pre-built build
>>> packages
>>>
>>> -M
>>
>> Yes, current design supports this scenario, i.e. if some packages are already pre-built, HOB will notice that and won't build them again.
> 
> It would be nice to be able to skip the package generation if the RPM
> already exists somewhere. This could provide significant speedup above
> what is already provided by sstate-cache. Although other issues might
> need to be solved....

I think this falls in line with the proposed design. If we create the
images from package feeds we needn't build when the package feeds are
already available.

Of course with ambiguous terms like *somewhere* I'm not sure we're
thinking along exactly the same lines but we're definitely looking to
speed up and re-use in as many places as possible.

Cheers,
Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre


  parent reply	other threads:[~2011-10-25 18:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21  3:16 Proposed roadmap and design for Hob improvement Yu, Ke
2011-10-21 15:54 ` Koen Kooi
2011-10-24  2:39   ` Yu, Ke
2011-10-21 21:13 ` McClintock Matthew-B29882
2011-10-24  3:12   ` Yu, Ke
2011-10-25 16:08     ` McClintock Matthew-B29882
2011-10-25 17:16       ` Mark Hatle
2011-10-25 18:09       ` Joshua Lock [this message]
2011-10-25 18:30         ` McClintock Matthew-B29882

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=4EA6FB40.7050600@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=yocto@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.