All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] rm_work
Date: Wed, 11 Apr 2007 08:50:47 +0200	[thread overview]
Message-ID: <200704110850.48209.openembedded@hrw.one.pl> (raw)
In-Reply-To: <1176049069.5844.6.camel@localhost.localdomain>

Dnia niedziela, 8 kwietnia 2007, Richard Purdie napisał:

> Even if you do this in bitbake itself, what happens if two tasks want
> to run last before do_build? Which do you choose?

> My thoughts are that we need to improve the way we specify tasks to be
> able to specify this kind of relationship more accurately. Even the
> form:
>
> addtask rm_work before do_build after do_package_write do_deploy
>
> where the tasks might not always exist might be enough to get things
> working?

I wrote rm_work.bbclass few years ago and it was always known as 'you can 
hit your own foot' solution due to lack of possibility to define WHEN 
exactly task will be started:

addtask rm_work right_before do_build after all_other_tasks

Maybe rm_work.bbclass should do:

BB_DEFAULT_TASK = "rm_work"
addtask rm_work after do_build

But I did not tested it yet (got that idea during Easter).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

                            It is your destiny.
                            		-- Darth Vader





  reply	other threads:[~2007-04-11  6:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 10:11 [RFC] rm_work Koen Kooi
2007-04-07 10:34 ` Holger Freyther
2007-04-07 10:41   ` Koen Kooi
2007-04-07 12:25     ` Rod Whitby
2007-04-07 22:03     ` Holger Freyther
2007-04-08 12:07       ` Koen Kooi
2007-04-08 12:21         ` Koen Kooi
2007-04-10 11:31           ` Michael 'Mickey' Lauer
2007-04-08 16:17       ` Richard Purdie
2007-04-11  6:50         ` Marcin Juszkiewicz [this message]
2007-04-11  6:55           ` Marcin Juszkiewicz
2007-04-11  8:41             ` Richard Purdie
2007-04-13 19:27           ` Koen Kooi
2007-04-13 22:08             ` Richard Purdie
2007-04-10 10:18   ` Florian Boor
2007-04-08 16:13 ` Richard Purdie
2007-04-08 17:01   ` Koen Kooi
2007-04-08 21:58     ` Richard Purdie

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=200704110850.48209.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --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.