From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Remove wildcard from SRC_URI
Date: Tue, 19 Feb 2013 18:47:30 -0600 [thread overview]
Message-ID: <1361321252-14982-1-git-send-email-mark.hatle@windriver.com> (raw)
This patch set removes the wild cards from the SRC_URI of both libpam
and the man recipes.
When FILESEXTRAPATHS is used in a bbappend file to add extra search paths,
bitbake's fetch2 unpack() doesn't properly handle a wildcard when used
in the SRC_URI field of the original recipe's bb file.
We can unpack failures, I've even seen a report of a fetch failure. We
resolve this by avoiding wild cards in SRC_URI!
I have verified that both before and after the change, the contents of the
source code and other components in these recipes are the same.
I suggest that we make wildcards in the SRC_URI field illegal, either via
a sanity check or within bitbake itself.
next 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 Mark Hatle [this message]
2013-02-20 0:47 ` [PATCH 1/2] man: Remove wildcard from SRC_URI Mark Hatle
2013-02-20 0:47 ` [PATCH 2/2] libpam: Avoid wildcards in the SRC_URI Mark Hatle
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-1-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