From: Bian Naimeng <biannm@cn.fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH]lsof: avoid creating directory ${DL_DIR}/${WORKDIR}/lsof_${PV}
Date: Fri, 09 Aug 2013 11:09:40 +0800 [thread overview]
Message-ID: <52045D74.2040703@cn.fujitsu.com> (raw)
lsof: avoid creating directory ${DL_DIR}/${WORKDIR}/lsof_${PV}.
Set LOCALSRC as SRC_URI will make do_unpack mkdir ${DL_DIR}/${WORKDIR}/lsof_${PV},
it's not good while multiuser sharing ${DL_DIR}.
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
---
meta/recipes-extended/lsof/lsof_4.87.bb | 15 +++++++--------
1 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/meta/recipes-extended/lsof/lsof_4.87.bb b/meta/recipes-extended/lsof/lsof_4.87.bb
index 2f425aa..222ede8 100644
--- a/meta/recipes-extended/lsof/lsof_4.87.bb
+++ b/meta/recipes-extended/lsof/lsof_4.87.bb
@@ -10,17 +10,16 @@ SRC_URI = "ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_${PV}.tar.bz2"
SRC_URI[md5sum] = "80e2a76d0e05826db910ec88e631296c"
SRC_URI[sha256sum] = "dfdd3709d82bc79ccdf3e404b84aafa9aede5948642a824ecaefd0aac589da2c"
-LOCALSRC = "file://${WORKDIR}/lsof_${PV}/lsof_${PV}_src.tar"
S = "${WORKDIR}/lsof_${PV}_src"
-LIC_FILES_CHKSUM = "file://${S}/00README;beginline=645;endline=679;md5=964df275d26429ba3b39dbb9f205172a"
+LIC_FILES_CHKSUM = "file://00README;beginline=645;endline=679;md5=964df275d26429ba3b39dbb9f205172a"
-python do_unpack () {
- bb.build.exec_func('base_do_unpack', d)
- src_uri = d.getVar('SRC_URI')
- d.setVar('SRC_URI', '${LOCALSRC}')
- bb.build.exec_func('base_do_unpack', d)
- d.setVar('SRC_URI', src_uri)
+python do_unpack_append () {
+ bb.build.exec_func('do_unpack_realsrc', d)
+}
+
+do_unpack_realsrc () {
+ tar x --no-same-owner -f ${WORKDIR}/lsof_${PV}/lsof_${PV}_src.tar -C ${WORKDIR}
}
export LSOF_OS = "${TARGET_OS}"
--
1.7.7
reply other threads:[~2013-08-09 3:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52045D74.2040703@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=openembedded-core@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.