From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate: Truncate PV in sstate filenames that are too long
Date: Wed, 31 Jul 2019 12:13:47 +0100 [thread overview]
Message-ID: <20190731111347.GA27256@mcrowe.com> (raw)
In-Reply-To: <6b194922-8aa4-f2c1-645b-ace8331ae532@windriver.com>
On Tuesday 30 July 2019 at 09:14:01 -0500, Mark Hatle wrote:
> Richard mentioned in the bitbake-devel thread that there may be external tools
> using some of the components. I'm not sure how to even identify what those
> tools are at this time, but a new sstate version entry may be enough to start to
> deal with them.
We have a couple of tools that know the format of sstate cache files:
The first tool[1] processes locked-sigs.inc to update the atime of any
files that would be necessary for the build. (We discovered that relying on
actually building to update atime was insufficient since it skipped sstate
files that were only necessary in order to build others.)
The second tool is simpler and just expires sstate files that haven't been
accessed in a while. We have a handful of different expiry policies by PN,
so we need to understand where that is in the filename. This tool needs to
cope with a cache populated by a mixture of oe-core versions, so any change
in format risks complicating it.
Mike.
[1] http://lists.openembedded.org/pipermail/openembedded-core/2016-April/120227.html
next prev parent reply other threads:[~2019-07-31 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 11:01 [PATCH] sstate: Truncate PV in sstate filenames that are too long Mike Crowe
2019-07-30 13:25 ` Mark Hatle
2019-07-30 13:49 ` Mike Crowe
2019-07-30 14:14 ` Mark Hatle
2019-07-31 11:13 ` Mike Crowe [this message]
2019-07-31 17:41 ` Mike Crowe
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=20190731111347.GA27256@mcrowe.com \
--to=mac@mcrowe.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 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.