Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: SSTATE builds more broken than I thought
Date: Fri, 12 Nov 2010 01:35:35 -0700	[thread overview]
Message-ID: <4CDCFC57.20909@mlbassoc.com> (raw)
In-Reply-To: <1289550656.1272.3179.camel@rex>

On 11/12/2010 01:30 AM, Richard Purdie wrote:
> On Fri, 2010-11-12 at 01:18 -0700, Gary Thomas wrote:
>>> Are these all files or are they symlinks? Are they just present for
>>> deploy-ipk or are there others?
>>
>> They are files.
>>
>> Sorry, but I don't understand your other question.  These are the only
>> extra files polluting the tree, except for Python *.py? object files
>> which are also always created.
>
> Are there any files related to other sstate tasks such as
> populate-sysroot*.tgz or package*.tgz or is there just *deploy-ipk*.tgz?
>
> In other words I'm wondering if this is something specific to the
> deploy-ipk sstate task...

The only extra files created are *deploy-ipk*.tgz
This most certainly is restricted to the deploy-ipk sstate task and only
happens if SSTATE_MIRRORS is defined.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2010-11-12  8:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 23:27 SSTATE builds more broken than I thought Gary Thomas
2010-11-12  5:32 ` Richard Purdie
2010-11-12  8:18   ` Gary Thomas
2010-11-12  8:30     ` Richard Purdie
2010-11-12  8:35       ` Gary Thomas [this message]
2010-11-12 23:31         ` Richard Purdie
2010-11-12 23:55           ` Gary Thomas
2010-11-14 17:58             ` Richard Purdie
2010-11-15  1:13               ` Tian, Kevin
2010-11-15  1:36                 ` Tian, Kevin
2010-11-15  3:29                   ` Tian, Kevin
2010-11-15  4:06               ` Tian, Kevin

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=4CDCFC57.20909@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.org \
    --cc=rpurdie@linux.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