From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] conditional patch-tool dep
Date: Tue, 21 Dec 2010 18:19:58 +0100 [thread overview]
Message-ID: <1292951999-18969-1-git-send-email-rep.dot.nop@gmail.com> (raw)
Hi,
If a recipe doesn't reference any patch then patching doesn't make sense
and neither does depending on patch-tool.
I didn't look yet if i can say
addtask patch after do_unpack if needs_patching_at_all(d)
(or something like that).
So, for a start, don't depend do_patch on the patch tool if there is no
patch in the SRC_URI.
untested.
PS: There should be some oe.is_compressed(uri) shorthand that is used to
decide if an uri is in a compressed format, imho.
Bernhard Reutner-Fischer (1):
patch.bbclass: conditional patch-tool dependency
classes/patch.bbclass | 21 +++++++++++++++++++--
1 files changed, 19 insertions(+), 2 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-12-21 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 17:19 Bernhard Reutner-Fischer [this message]
2010-12-21 17:19 ` [PATCH] patch.bbclass: conditional patch-tool dependency Bernhard Reutner-Fischer
2011-01-03 19:54 ` Bernhard Reutner-Fischer
2011-01-05 12:39 ` Leon Woestenberg
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=1292951999-18969-1-git-send-email-rep.dot.nop@gmail.com \
--to=rep.dot.nop@gmail.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.