From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Phil Blundell <philb@gnu.org>
Subject: Re: [RFC PATCH 1/2] image.bbclass, kernel.bbclass: create warning file about deleting deploydir files
Date: Tue, 23 Aug 2011 12:08:08 -0700 [thread overview]
Message-ID: <4E53FA98.1060909@linux.intel.com> (raw)
In-Reply-To: <201108191127.48228.paul.eggleton@linux.intel.com>
On 08/19/2011 03:27 AM, Paul Eggleton wrote:
> 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.
I don't see it as having the same negative conotation as the force
options to things like rpm and dpkg. Here it just means "I really want
to run this specific task again, even if you already ran it, likely
because I know I did something to undo what you just did." :-)
>
> Cheers,
> Paul
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-08-23 19:12 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
2011-08-23 19:08 ` Darren Hart [this message]
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=4E53FA98.1060909@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox