From: Tom Rini <trini@konsulko.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: sstate hash equivalence breaks rm_work
Date: Mon, 4 Mar 2019 07:21:42 -0500 [thread overview]
Message-ID: <20190304122142.GN5026@bill-the-cat> (raw)
In-Reply-To: <CAJTo0LaOGr4iJh0r1s=wWOy3XA47-L+++Dq+zQOV5hD3LCD4Kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Mon, Mar 04, 2019 at 10:17:21AM +0000, Burton, Ross wrote:
> On Sun, 3 Mar 2019 at 22:52, Tom Rini <trini@konsulko.com> wrote:
> > SSTATE_DIR = "${HOME}/work/OE/sstate-cache-${DISTRO_VERSION}${TARGET_VENDOR}"
>
> FWIW there isn't much point in isolating sstate like that. You'll
> just rebuild stuff that would have been available.
Martin already chimed in, but this is my "copy this to every project"
site.conf file. I do modify that base path a little bit for per
project, But easily removable state is good and important, especially
when chasing "recipe for proprietary thing behaves badly" bugs.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2019-03-04 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 20:47 sstate hash equivalence breaks rm_work Tom Rini
2019-03-03 21:21 ` Joshua Watt
2019-03-03 21:25 ` Tom Rini
2019-03-03 22:11 ` Joshua Watt
2019-03-03 22:20 ` Joshua Watt
2019-03-03 22:51 ` Tom Rini
2019-03-04 10:17 ` Burton, Ross
2019-03-04 10:26 ` Martin Jansa
2019-03-04 10:45 ` Burton, Ross
2019-03-04 10:56 ` Martin Jansa
2019-03-04 12:21 ` Tom Rini [this message]
2019-03-04 15:58 ` Tom Rini
2019-03-04 16:06 ` Richard Purdie
2019-03-04 16:14 ` Tom Rini
2019-03-04 16:21 ` Richard Purdie
2019-03-04 16:38 ` Tom Rini
2019-03-04 16:17 ` Joshua Watt
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=20190304122142.GN5026@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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