From: Dan McGregor <danismostlikely@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-networking][PATCH] netcat-openbsd: fixup patching
Date: Mon, 12 May 2014 10:30:46 -0600 [thread overview]
Message-ID: <CACS+7ZQ1i2nTKLcD+toOBN2BPA9PE=zzdD05oDLmPkCKco-NUA@mail.gmail.com> (raw)
From: Dan McGregor <dan.mcgregor@usask.ca>
Do the patching in the do_patch phase instead of the compile
phase. That way if the compile phase needs to be rerun
patching isn't attempted a second time.
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
---
.../recipes-support/netcat/netcat-openbsd_1.105.bb | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
b/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
index 4474e1d..4489656 100644
--- a/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
+++ b/meta-networking/recipes-support/netcat/netcat-openbsd_1.105.bb
@@ -15,11 +15,20 @@ SRC_URI[netcat-patch.sha256sum] =
"eee759327ffea293e81d0dde67921b7fcfcad279ffd7a
S = "${WORKDIR}/${BPN}-${PV}"
+netcat_do_patch() {
+ cd ${S}
+ while read line; do patch -p1 < ${WORKDIR}/debian/patches/$line;
done < ${WORKDIR}/debian/patches/series
+}
+
+python do_patch() {
+ bb.build.exec_func('netcat_do_patch', d)
+ bb.build.exec_func('patch_do_patch', d)
+}
+
do_configure[noexec] = "1"
do_compile() {
cd ${S}
- while read line; do patch -p1 < ${WORKDIR}/debian/patches/$line;
done < ${WORKDIR}/debian/patches/series
pkgrel=4
oe_runmake CFLAGS="$CFLAGS -DDEBIAN_VERSION=\"\\\"${pkgrel}\\\"\""
}
--
1.9.0
next reply other threads:[~2014-05-12 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:30 Dan McGregor [this message]
2014-06-04 1:43 ` [meta-networking][PATCH] netcat-openbsd: fixup patching Joe MacDonald
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='CACS+7ZQ1i2nTKLcD+toOBN2BPA9PE=zzdD05oDLmPkCKco-NUA@mail.gmail.com' \
--to=danismostlikely@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.