All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel@lists.openembedded.org
Subject: Re: RFC: Override expansion - changing the behaviour
Date: Wed, 01 Jun 2011 15:59:37 +0100	[thread overview]
Message-ID: <1306940377.27470.429.camel@rex> (raw)
In-Reply-To: <1306882804.27470.402.camel@rex>

To follow up on this, what kind of cleanup would this and some other
tweaks to bitbake allow?

This is my proof of concept:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/temp3&id=1ed909e8b9bac6ed88ffbbe6a100a42c4289f498

which cleans up native.bbclass and nativesdk.bbclass to be much cleaner
code with less strange side effects and hoops to jump through.

The main changes to bitbake after the original patch I posted were:

a) Add handlers before any data finalisation
b) Add a new "pre finalise" event

Cheers,

Richard




  reply	other threads:[~2011-06-01 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 23:00 RFC: Override expansion - changing the behaviour Richard Purdie
2011-06-01 14:59 ` Richard Purdie [this message]
2011-06-01 15:51   ` Chris Larson
2011-06-07 22:10 ` Joshua Lock
2011-06-07 22:16   ` Mark Hatle

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=1306940377.27470.429.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-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 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.