From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Watt <jpewhacker@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Uninative and sstate
Date: Thu, 04 Jan 2018 22:36:00 +0000 [thread overview]
Message-ID: <1515105360.30291.20.camel@linuxfoundation.org> (raw)
In-Reply-To: <1515103894.665.22.camel@gmail.com>
On Thu, 2018-01-04 at 16:11 -0600, Joshua Watt wrote:
> On Thu, 2018-01-04 at 22:00 +0000, Richard Purdie wrote:
> > There used to be an optimisation we made where we only did it when
> > we
> > needed to (using sstate). The move to RSS meant that we now always
> > have
> > to do it. I'd therefore guess you're using morty or older? On more
> > recent versions you'll see it always relocating. There are pros and
> > cons both ways.
> Yes we are using morty. I suppose that at least explains the
> behavior.
You'll find:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=morty&id=590ef99df7
4581e6b7595e545c12594012653de8
interesting (its on the stable branch now).
That was basically retrofitting some of this behaviour to morty to fix
bugs...
Cheers,
Richard
prev parent reply other threads:[~2018-01-04 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 20:15 Uninative and sstate Joshua Watt
2018-01-04 22:00 ` Richard Purdie
2018-01-04 22:11 ` Joshua Watt
2018-01-04 22:36 ` Richard Purdie [this message]
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=1515105360.30291.20.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jpewhacker@gmail.com \
--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