From: "Rasmus Villemoes" <rasmus.villemoes@prevas.dk>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: "OE Core mailing list" <openembedded-core@lists.openembedded.org>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Kjeld Flarup" <kfa@deif.com>,
"Per Nørgaard Christensen" <per.christensen@prevas.dk>,
"Paul Eggleton" <paul.eggleton@linux.intel.com>,
"Kurt Østergaard Frandsen" <kof@deif.com>
Subject: Re: [OE-core] file checksums versus SRC_URI globs
Date: Thu, 2 Jul 2020 08:42:00 +0200 [thread overview]
Message-ID: <c16556f1-5f7f-4562-77e2-7da33e5c345f@prevas.dk> (raw)
In-Reply-To: <20200701140321.wueczs4qd34rbhwh@qschulz>
On 01/07/2020 16.03, Quentin Schulz wrote:
> Hi Rasmus,
>
> On Wed, Jul 01, 2020 at 03:51:19PM +0200, Rasmus Villemoes wrote:
>> Hi,
>>
>> We have a recipe that uses
>>
>> SRC_URI += "file://somedir/*"
>>
>
> Glob aren't supported. Use "file://somedir/" instead.
Thanks, that actually works for one of the cases we have (there are
others that use globs which cannot be solved quite that simply, but for
now I'm just listing files explicitly instead).
However, I'm not sure that "globs aren't supported". The commit I
referenced clearly tried to make that work (better), it also "works" in
the sense of unpacking the expected things when building from scratch -
there's even
def test_local_wildcard(self):
tree = self.fetchUnpack(['file://a', 'file://dir/*'])
self.assertEqual(tree, ['a', 'dir/c', 'dir/d', 'dir/subdir/e'])
in bitbake/lib/bb/tests/fetch.py. And the two upstream recipes
connman-gnome_0.7.bb and matchbox-desktop_2.2.bb both use that exact
pattern.
So either
- this is a plain bug in the signature computation,
- documentation lacks a big fat warning that using globs in file://
should be avoided unless one has a fetish for tracking down bugs due to
confused sstate, or
- all code that makes glob patterns work should be ripped out so that it
is indeed not supported, thus eliminating this footgun.
Rasmus
next prev parent reply other threads:[~2020-07-02 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 13:51 file checksums versus SRC_URI globs Rasmus Villemoes
2020-07-01 14:03 ` [OE-core] " Quentin Schulz
2020-07-02 6:42 ` Rasmus Villemoes [this message]
[not found] ` <161DDC5BD88A8AE5.10798@lists.openembedded.org>
2020-07-09 19:31 ` Rasmus Villemoes
2020-08-25 14:03 ` Richard Purdie
[not found] ` <16202C67498F91AC.11682@lists.openembedded.org>
2020-08-05 8:21 ` Rasmus Villemoes
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=c16556f1-5f7f-4562-77e2-7da33e5c345f@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=kfa@deif.com \
--cc=kof@deif.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=per.christensen@prevas.dk \
--cc=quentin.schulz@streamunlimited.com \
--cc=richard.purdie@linuxfoundation.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