From: Richard Purdie <rpurdie@rpsys.net>
To: Michael Smith <msmith@cbnco.com>
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [Bitbake-dev] A new bitbake extension: .bbappend files
Date: Fri, 16 Jul 2010 17:24:16 +0100 [thread overview]
Message-ID: <1279297456.10837.1942.camel@rex> (raw)
In-Reply-To: <4C407EE5.6050802@cbnco.com>
On Fri, 2010-07-16 at 11:46 -0400, Michael Smith wrote:
> Richard Purdie wrote:
> > The idea is that if bitbake finds any X.bbappend files, when it loads
> > X.bb, it will also include these files after it parses the base .bb file
> > (but before finalise and the anonymous methods run). This means that
> > the .bbappend file can poke around and do whatever it might want to the
> > recipe to customise it.
>
> Does this do anything different than amendrecipes.bbclass?
Several people have mentioned the amend bbclass. This implements
something very similar in quite a different way as part of the bitbake
tool itself. There are advantages and disadvantages to doing this.
The features I liked about the bbappend approach was the small amount of
code change required to bitbake compared to the functionality it offers
and also the overhead of the bbappend code is minimal.
I also feel the bbappend format is slightly easier for users to
comprehend but that is subjective.
A downside is that the .bbappend applies to specific versions, not all
versions as amend.bbclass can be setup. There are ways that could be
changed.
The amend class has a greater degree of flexibility in that you can make
changes to the class and it could be argued not changing the core is an
advantage too.
Cheers,
Richard
next prev parent reply other threads:[~2010-07-16 16:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 14:25 A new bitbake extension: .bbappend files Richard Purdie
2010-07-16 14:35 ` George C. Huntington, III
2010-07-16 15:37 ` Carl Simonson
2010-07-16 15:46 ` [Bitbake-dev] " Michael Smith
2010-07-16 16:16 ` Chris Larson
2010-07-16 16:24 ` Richard Purdie [this message]
2010-07-16 16:53 ` Frans Meulenbroeks
2010-07-18 8:12 ` Esben Haabendal
2010-07-18 10:06 ` Detlef Vollmann
2010-07-18 15:13 ` Chris Larson
2010-07-18 16:01 ` Detlef Vollmann
2010-07-18 16:06 ` Chris Larson
2010-07-18 19:24 ` Detlef Vollmann
2010-07-18 20:25 ` Richard Purdie
2010-07-18 21:13 ` Detlef Vollmann
2010-07-19 8:31 ` Hauser, Wolfgang (external)
2010-07-18 19:47 ` Frans Meulenbroeks
2010-07-18 20:52 ` Chris Larson
2010-07-18 20:57 ` Frans Meulenbroeks
2010-07-19 0:02 ` Douglas Royds
2010-07-19 20:50 ` Tom Rini
2010-07-19 21:22 ` Chris Larson
2010-07-19 21:24 ` Chris Larson
2010-07-20 7:28 ` Frans Meulenbroeks
2010-07-20 14:06 ` Chris Larson
2010-07-20 15:19 ` Tom Rini
2010-07-20 15:50 ` Tom Rini
2010-07-20 15:52 ` Michael Smith
2010-07-20 16:06 ` Chris Larson
2010-07-20 16:29 ` Frans Meulenbroeks
2010-07-20 16:54 ` Chris Larson
2010-08-03 10:04 ` Frans Meulenbroeks
2010-08-03 12:53 ` Richard Purdie
2010-08-03 19:30 ` Khem Raj
2010-08-03 13:26 ` [Bitbake-dev] " Richard Purdie
2010-08-03 14:13 ` Chris Larson
2010-08-04 4:09 ` Khem Raj
2010-08-04 14:40 ` Richard Purdie
2010-08-04 19:00 ` Khem Raj
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=1279297456.10837.1942.camel@rex \
--to=rpurdie@rpsys.net \
--cc=bitbake-dev@lists.berlios.de \
--cc=msmith@cbnco.com \
--cc=openembedded-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.