From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Subject: Re: [PATCH] console-tools: removed wildcard from SRC_URI
Date: Wed, 27 Jul 2011 17:04:35 -0700 [thread overview]
Message-ID: <4E30A793.4080202@linux.intel.com> (raw)
In-Reply-To: <1311604062-14337-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On 07/25/2011 07:27 AM, Enrico Scholz wrote:
> From: Enrico Scholz<enrico.scholz@informatik.tu-chemnitz.de>
>
> Wildcards in SRC_URI are not supported by oe-core and work only
> when last (or first?) FILESPATH element points to the containing
> directory. Specifying plain dir works fine for this recipe.
>
> Signed-off-by: Enrico Scholz<enrico.scholz@informatik.tu-chemnitz.de>
> ---
> .../console-tools/console-tools_0.3.2.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/console-tools/console-tools_0.3.2.bb b/meta/recipes-core/console-tools/console-tools_0.3.2.bb
> index 5b09105..7baace6 100644
> --- a/meta/recipes-core/console-tools/console-tools_0.3.2.bb
> +++ b/meta/recipes-core/console-tools/console-tools_0.3.2.bb
> @@ -11,7 +11,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/lct/console-tools-${PV}.tar.gz \
> file://compile.patch;patch=1 \
> file://kbdrate.patch;patch=1 \
> file://uclibc-fileno.patch;patch=1 \
> - file://config/*.m4"
> + file://config"
>
> SRC_URI[md5sum] = "bf21564fc38b3af853ef724babddbacd"
> SRC_URI[sha256sum] = "eea6b441672dacd251079fc85ed322e196282e0e66c16303ec64c3a2b1c126c2"
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-07-28 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 14:27 [PATCH] console-tools: removed wildcard from SRC_URI Enrico Scholz
2011-07-28 0:04 ` Saul Wold [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=4E30A793.4080202@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=enrico.scholz@informatik.tu-chemnitz.de \
--cc=enrico.scholz@sigma-chemnitz.de \
--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.