From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 2/2] libpam: Avoid wildcards in the SRC_URI
Date: Tue, 19 Feb 2013 18:47:32 -0600 [thread overview]
Message-ID: <1361321252-14982-3-git-send-email-mark.hatle@windriver.com> (raw)
In-Reply-To: <1361321252-14982-1-git-send-email-mark.hatle@windriver.com>
[ CQID: WIND00402802 ]
Remove the wildcard from the SRC_URI. This causes problems when you .bbappend
and add a FILESEXTRAPATHS entry. The unpack task may be unable to find the
files to unpack leading to an error.
Avoid wildcards at all costs...
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
---
meta/recipes-extended/pam/libpam_1.1.6.bb | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/pam/libpam_1.1.6.bb b/meta/recipes-extended/pam/libpam_1.1.6.bb
index 93c98c0..011769a 100644
--- a/meta/recipes-extended/pam/libpam_1.1.6.bb
+++ b/meta/recipes-extended/pam/libpam_1.1.6.bb
@@ -11,7 +11,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=7eb5c1bf854e8881005d673599ee74d3"
SRC_URI = "http://linux-pam.org/library/Linux-PAM-${PV}.tar.bz2 \
file://99_pam \
- file://pam.d/* \
+ file://pam.d/common-account \
+ file://pam.d/common-auth \
+ file://pam.d/common-password \
+ file://pam.d/common-session \
+ file://pam.d/common-session-noninteractive \
+ file://pam.d/other \
file://libpam-xtests.patch \
file://destdirfix.patch \
"
@@ -30,7 +35,7 @@ EXTRA_OECONF = "--with-db-uniquename=_pam \
CFLAGS_append = " -fPIC "
-PR = "r2"
+PR = "r3"
S = "${WORKDIR}/Linux-PAM-${PV}"
--
1.8.1.2.545.g2f19ada
prev parent reply other threads:[~2013-02-20 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 0:47 [PATCH 0/2] Remove wildcard from SRC_URI Mark Hatle
2013-02-20 0:47 ` [PATCH 1/2] man: " Mark Hatle
2013-02-20 0:47 ` Mark Hatle [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=1361321252-14982-3-git-send-email-mark.hatle@windriver.com \
--to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox