On 2016-01-25 10:52 AM, Richard Purdie wrote:
On Mon, 2016-01-25 at 10:47 -0500, Bruce Ashfield wrote:
On 2016-01-25 10:07 AM, Richard Purdie wrote:
If we don't do this, the deploy sstate object contains an every
increasing number of modules tarballs and kernel images, one per
execution of "-c
On Mon, 2016-01-25 at 10:47 -0500, Bruce Ashfield wrote:
> On 2016-01-25 10:07 AM, Richard Purdie wrote:
> > If we don't do this, the deploy sstate object contains an every
> > increasing number of modules tarballs and kernel images, one per
> > execution of "-c deploy -f".
> >
>
> Stupid questio
On 2016-01-25 10:07 AM, Richard Purdie wrote:
If we don't do this, the deploy sstate object contains an every
increasing number of modules tarballs and kernel images, one per
execution of "-c deploy -f".
Stupid question, since my sstate/deploy foo is weak at times.
Does this mean that only a s
If we don't do this, the deploy sstate object contains an every
increasing number of modules tarballs and kernel images, one per
execution of "-c deploy -f".
Cleaning the directory before we start makes things much tidier.
Signed-off-by: Richard Purdie
diff --git a/meta/classes/kernel.bbclass b
