From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path
Date: Wed, 11 Jul 2012 21:20:45 +0100 [thread overview]
Message-ID: <1342038045.11939.39.camel@ted> (raw)
In-Reply-To: <CAJTo0LYQTGihjGz5iYC+L34QY4gf00urFqr92MyiHrwWyMC==A@mail.gmail.com>
On Wed, 2012-07-11 at 20:54 +0100, Burton, Ross wrote:
> On 11 July 2012 20:01, Chris Larson <clarson@kergoth.com> wrote:
> > That's one possibility. The other would be to treat _append/_prepended
> > functions as independent entities. Rather than concatenating
> > functions, it'd add them to the prefuncs/postfuncs or equivalent.
> > Without concatenation, there'd be no issues with mismatches.
>
> I always thought it would be best to give each append/prepend chunk a
> unique name and then call them sequentially instead of gluing them
> together.
Some of them even rely on variables set in other fragments. I think I
killed the one example I saw but there still could be something
potentially relying on this :(
I agree we need to fix this. I'm tempted to have the python parser just
error on finding tab indentation.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-11 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:00 [PATCH 0/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
2012-07-11 16:00 ` [PATCH 1/1] " Peter Seebach
2012-07-11 16:12 ` Richard Purdie
2012-07-11 16:33 ` Peter Seebach
2012-07-11 17:36 ` Richard Purdie
2012-07-11 17:56 ` Ross Burton
2012-07-11 18:54 ` Peter Seebach
2012-07-11 19:01 ` Chris Larson
2012-07-11 19:54 ` Burton, Ross
2012-07-11 20:20 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-11 20:31 [PATCH 0/1] package.bbclass: Allow overriding of debugedit base path Peter Seebach
2012-07-11 20:31 ` [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
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=1342038045.11939.39.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox