From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Package selection
Date: Mon, 18 Jun 2012 21:46:40 -0700 [thread overview]
Message-ID: <4FE00430.2070307@gmail.com> (raw)
In-Reply-To: <CAMKF1sr6ekWbucQzJD+uM7ToH2mZfQ9yYVOPbhOKr8uLZjCTrQ@mail.gmail.com>
On 06/18/2012 09:40 PM, Khem Raj wrote:
> On Mon, Jun 18, 2012 at 9:34 PM, j <vwyodapink@gmail.com> wrote:
>>> Also, you need to bitbake -c cleanall <your-package> to make bitbake
>>> forget it
>>
>> Isnt bitbake -c cleansstate <your-package> a better method of cleaning a
>> build you want to do again?
>>
>> If not does anyone know what the actual difference is?
> clean - cleans the builddir
> cleansstate - cleans builddir as well as shared state copy of this
> package if any
> cleanall - clean builddir, shared state and the downloaded src tar
> file from DL_DIR
>
> you usually only should need clean in general. cleansstate should be seldom used
> but its preferred to see why cleansstate is needed and if there is
> anything wrong
> with sstate we would like to know.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Thanks Khem, been wondering that info just had not looked into it as of
yet. Makes perfect sense now.
prev parent reply other threads:[~2012-06-19 4:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 16:57 Package selection Dallas Clement
2012-06-18 18:26 ` Mark Hatle
2012-06-18 18:31 ` Khem Raj
2012-06-19 0:32 ` Ciprian Ciubotariu
2012-06-19 1:19 ` Dallas Clement
2012-06-19 4:34 ` j
2012-06-19 4:40 ` Khem Raj
2012-06-19 4:46 ` j [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=4FE00430.2070307@gmail.com \
--to=vwyodapink@gmail.com \
--cc=openembedded-devel@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