From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5 V2] refactor the archiver*.bbclass
Date: Tue, 4 Mar 2014 09:27:13 +0800 [thread overview]
Message-ID: <53152BF1.3050806@windriver.com> (raw)
In-Reply-To: <CAJTo0Lb=a40bP3R-YtSoxeixcKaPjASwiXU8617cfMSqx4cKMw@mail.gmail.com>
Hi Ross,
Thanks for your reply, please see my comments inline.
On 02/27/2014 09:05 PM, Burton, Ross wrote:
> Hi Robert,
>
> Having a look at this and playing with my own toy archiver makes me
> think that this shouldn't be using the postfuncs at all.
>
Yes, I gree as we had talked.
> The main task, deploy_archives, should depend on the subtasks that it
> needs and be simply ordered before do_build. I see that your code
> does this but changes it to be before do_rootfs if the recipe is an
> image: I'm not sure I understand why this is as do_rootfs is just a
> task that executes before do_build so this shouldn't need
> special-casing.
>
This part of code is derived from the previous archiver.bbclass, I will
remove it.
> Why did you implement the subtasks as postfuncs instead of normal
> tasks? This has the effect of causing more work to be done if the
What I had thought was that use the postfuncs will always make sure it
will run, for example, if do_unpack runs, then do_unpack[postfuncs] will
always run, but if we use a new task:
addtask do_ar_unpacked after do_unpack before do_patch
If do_patch doesn't run, the do_ar_unpacked would not run either, as had
talked, we will use new ${S}, so this problem will be gone, I will use
new tasks.
> archiver needs to run: for example do_ar_unpacked() is a postfunc on
> do_unpack so either enabling/disabling the archiver or editing the
> archiver class causes the do_unpack hash to change, so everything
> afterwards (do_patch, do_configure, do_compile, ...) has to
> re-execute.
>
> My toy archiver was implemented as a new task which is after do_fetch
> but before do_build. This means that it executes after fetch has
> completed but is outside of the
> fetch->patch->configure->compile->install sequence.
>
> https://github.com/rossburton/meta-ross/blob/master/classes/rearchiver.bbclass
>
> (it also has a way of archiving the original sources in a way that
> actually archives the original sources)
Great, thanks, I will send a V3 sooner.
// Robert
>
> Ross
>
>
prev parent reply other threads:[~2014-03-04 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 15:56 [PATCH 0/5 V2] refactor the archiver*.bbclass Robert Yang
2014-02-24 15:56 ` [PATCH 1/5] classes/archive*.bbclass: remove archive-*-source.bbclass Robert Yang
2014-02-24 15:56 ` [PATCH 2/5] archiver.bbclass: refactor it Robert Yang
2014-02-25 12:38 ` Burton, Ross
2014-02-25 13:04 ` Robert Yang
2014-02-24 15:56 ` [PATCH 3/5] package_rpm.bbclass: archive the source to srpm package Robert Yang
2014-02-24 15:56 ` [PATCH 4/5] archiver.bbclass: move a few code to copyleft_compliance.bbclass Robert Yang
2014-02-24 15:56 ` [PATCH 5/5] local.conf.sample.extended: update for the archiver Robert Yang
2014-02-25 12:40 ` [PATCH 0/5 V2] refactor the archiver*.bbclass Burton, Ross
2014-02-25 13:05 ` Robert Yang
2014-02-27 13:05 ` Burton, Ross
2014-03-04 1:27 ` Robert Yang [this message]
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=53152BF1.3050806@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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