All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Lifecycle issues in Bitbake
Date: Fri, 23 Jan 2015 10:33:58 +0000	[thread overview]
Message-ID: <3577015.nPVb6vKuGn@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <1421938639.19798.17.camel@linuxfoundation.org>

Hi Richard,

On Thursday 22 January 2015 14:57:19 Richard Purdie wrote:
> Looking at and thinking about:
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5187
> 
> We have several issues. Firstly, DATE and TIME are locked in stone when
> the base configuration is parsed. This may cause images to overwrite
> previous versions for example if DATE and TIME are not re-evaluated. We
> could fix this by specifically setting DATE and TIME in bitbake at
> BuildStart?

We could certainly do this. Another mechanism I did think about was to have 
some way of indicating to BitBake that on buildstart the value should be reset 
to the immediate evaluation of an expression; perhaps a varflag. At least that 
way we could handle other such variables, although it's conceivable that 
having built-in DATE and TIME in BitBake wouldn't be the worst thing in the 
world.
 
> Secondly, there is one cooker log file opened for the duration of the
> cooker lifecycle. This is a cooker log, not a log of each build so that
> is perhaps not surprising (and is the core problem in the above bug).
> There is no overwriting of the log file, it just keeps growing with each
> build.
> 
> We could trigger knotty to write out build specific log files based on
> the BuildStart/Finish events?

Yes I think we should do this.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2015-01-23 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 14:57 Lifecycle issues in Bitbake Richard Purdie
2015-01-22 16:39 ` Christopher Larson
2015-01-23 10:33 ` Paul Eggleton [this message]
2015-01-23 18:05   ` Alex Damian

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=3577015.nPVb6vKuGn@peggleto-mobl5.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.