From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH RFC 1/3] insane: Split do_package_qa into a separate task (from do_package)
Date: Fri, 11 Jul 2014 18:40:48 +0100 [thread overview]
Message-ID: <1405100448.21289.88.camel@ted> (raw)
In-Reply-To: <CAP9ODKrwE-vNz=NcZ7pntPiCaqqdVNkMnOiNGy2yTCJnsNxUBA@mail.gmail.com>
On Fri, 2014-07-11 at 13:46 -0300, Otavio Salvador wrote:
> On Fri, Jul 11, 2014 at 10:22 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Fri, 2014-07-11 at 09:14 -0300, Otavio Salvador wrote:
> ...
> >> > I would not recommend setting variables in function prepends like this,
> >> > its ugly and error prone, as you've just found out.
> >>
> >> Any suggested better way of to do it?
> >
> > The anonymous python fragment should be fine, it sets the data at the
> > right level, the global recipe level rather than burying it in some
> > task.
>
> and in case we need to do it for the packages split from the
> do_package_split? Use the hook mechanism?
That will not work, if you set data in the do_package task, the
do_package_q task cannot see it.
You'd probably have to add a prefunc to do_package_qa to set the right
skip variables if you needed to that since the package names wouldn't be
known until then.
Cheers,
Richard
next prev parent reply other threads:[~2014-07-11 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 20:15 [PATCH RFC 1/3] insane: Split do_package_qa into a separate task (from do_package) Richard Purdie
2014-07-11 2:43 ` Otavio Salvador
2014-07-11 8:27 ` Richard Purdie
2014-07-11 12:14 ` Otavio Salvador
2014-07-11 13:22 ` Richard Purdie
2014-07-11 16:46 ` Otavio Salvador
2014-07-11 17:40 ` Richard Purdie [this message]
2014-07-11 19:37 ` Burton, Ross
2014-07-11 19:46 ` Otavio Salvador
2014-07-11 21:11 ` Richard Purdie
2014-07-18 10:26 ` Martin Jansa
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=1405100448.21289.88.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=meta-freescale@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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