From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 1/2] image.bbclass, kernel.bbclass: create warning file about deleting deploydir files
Date: Fri, 19 Aug 2011 11:27:48 +0100 [thread overview]
Message-ID: <201108191127.48228.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1313606497.3630.16.camel@lenovo.internal.reciva.com>
On Wednesday 17 August 2011 19:41:37 Phil Blundell wrote:
> On Wed, 2011-08-17 at 19:37 +0100, Paul Eggleton wrote:
> > +Files in the deploy directory will not be re-created automatically if
> > you +delete them. If you do delete a file, you will need to run:
> > +
> > + bitbake -c clean TARGET
> > + bitbake TARGET
> > +
> > +where TARGET is the name of the appropriate package or target e.g.
> > +"virtual/kernel" for the kernel, an image, etc.
>
> Doesn't it suffice to run "bitbake -f -c deploy TARGET"?
I guess it would, but I'm not sure we really want to be encouraging users to
use -f.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-19 10:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 18:37 [RFC PATCH 0/2] Couple of fixes to help new users Paul Eggleton
2011-08-17 18:37 ` [RFC PATCH 1/2] image.bbclass, kernel.bbclass: create warning file about deleting deploydir files Paul Eggleton
2011-08-17 18:41 ` Phil Blundell
2011-08-19 10:27 ` Paul Eggleton [this message]
2011-08-23 19:08 ` Darren Hart
2011-08-23 20:07 ` Paul Eggleton
2011-08-23 21:39 ` Koen Kooi
2011-08-23 21:52 ` Paul Eggleton
2011-08-22 21:01 ` Koen Kooi
2011-08-23 6:44 ` Anders Darander
2011-08-23 8:33 ` Koen Kooi
2011-08-23 9:22 ` Phil Blundell
2011-08-23 9:32 ` Paul Eggleton
2011-08-23 10:37 ` Phil Blundell
2011-08-17 18:37 ` [RFC PATCH 2/2] sanity.bbclass: add optional untested host distro warning Paul Eggleton
2011-08-23 15:14 ` [RFC PATCH 0/2] Couple of fixes to help new users Saul Wold
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=201108191127.48228.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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.