Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/7] Developer workflow improvements
Date: Sat, 13 Dec 2014 22:47:16 -0500	[thread overview]
Message-ID: <548D0844.4010404@linaro.org> (raw)
In-Reply-To: <4747988.F41N2UaoOI@peggleto-mobl5.ger.corp.intel.com>


On 12/11/14 12:14, Paul Eggleton wrote:
>> It's not supposed to behave this way, although I have reproduced it here - I
>> think I hadn't actually tested rebuilding an image with a recipe in the
>> workspace added to the image. The problem is that the do_compile task is
>> being marked as nostamp, but the way bitbake behaves now, that doesn't
>> cause any dependent task signatures to be changed and thus no dependent
>> tasks get run afterwards. Either I'll have to change that or work out a
>> different way of ensuring do_compile and dependent tasks get run  - either
>> way, you should only have to run a build that calls for the recipe (be it
>> the recipe itself or something that depends upon it), no cleaning/resetting
>> should be needed. I'll try to fix this tomorrow.
> OK, I've fixed this on the branch as well. You should now find that rebuilding 
> the image always triggers a compile -> install -> package etc. of the 
> recipe(s) in the workspace first. (It'll end up triggering other recipes to 
> rebuild as well if they are in the chain; we may have to address that 
> differently later for cases where that's annoying).

Ok great. I've re-tested and it all seems good.


      parent reply	other threads:[~2014-12-14  3:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 17:28 [RFC PATCH 0/7] Developer workflow improvements Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 1/7] lib/oe/patch: fall back to patch if git apply fails Paul Eggleton
2014-11-25 17:40   ` Paul Barker
2014-11-25 17:58     ` Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 2/7] lib/oe/patch: auto-commit when falling back from git am Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 3/7] lib/oe/patch: use --keep-cr with " Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 4/7] scripts/recipetool: Add a recipe auto-creation script Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 5/7] lib/oe: add recipeutils module Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 6/7] scripts/devtool: add development helper tool Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 7/7] scripts/devtool: Support deploy/undeploy function Paul Eggleton
2014-11-25 17:51 ` [RFC PATCH 0/7] Developer workflow improvements Paul Barker
2014-11-25 18:34   ` Paul Eggleton
2014-11-25 19:56 ` Trevor Woerner
2014-11-26  9:02   ` Paul Eggleton
2014-11-28 17:28 ` Trevor Woerner
2014-12-01 10:11   ` Paul Eggleton
2014-12-02  4:36     ` Trevor Woerner
2014-12-02 11:46       ` Paul Eggleton
2014-12-04 14:03         ` Trevor Woerner
2014-12-04 15:33           ` Paul Eggleton
2014-12-02  4:54 ` Trevor Woerner
2014-12-02 14:01   ` Paul Eggleton
2014-12-09 15:47     ` Trevor Woerner
2014-12-11 23:10       ` Trevor Woerner
2014-12-12 12:39         ` Paul Eggleton
     [not found] ` <54866CD7.1050102@linaro.org>
     [not found]   ` <7839390.odV1UMkpj8@peggleto-mobl5.ger.corp.intel.com>
2014-12-09 15:00     ` Trevor Woerner
2014-12-09 15:10       ` Paul Eggleton
2014-12-09 15:39         ` Trevor Woerner
2014-12-09 16:08           ` Paul Eggleton
2014-12-09 18:58             ` Trevor Woerner
2014-12-10 17:51               ` Paul Eggleton
2014-12-11 17:14                 ` Paul Eggleton
2014-12-11 18:30                   ` Trevor Woerner
2014-12-11 18:55                     ` Paul Eggleton
2014-12-11 19:16                       ` Trevor Woerner
2014-12-11 19:43                         ` Trevor Woerner
2014-12-11 21:35                           ` Paul Eggleton
2014-12-11 23:14                             ` Trevor Woerner
2014-12-12 13:01                             ` Otavio Salvador
2014-12-14  3:47                   ` Trevor Woerner [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=548D0844.4010404@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@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