From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>,
<nicolas.dechesne@linaro.org>, <vkraleti@codeaurora.org>
Subject: Re: [OE-core] [PATCH 0/2] Example of how prebuilt binaries and locked sstate could work
Date: Mon, 2 Nov 2020 09:01:02 +0000 [thread overview]
Message-ID: <20201102090100.GS1246345@korppu> (raw)
In-Reply-To: <20201101125302.350160-1-richard.purdie@linuxfoundation.org>
Hi,
On Sun, Nov 01, 2020 at 12:53:00PM +0000, Richard Purdie wrote:
> At the Yocto Project Summit, there was some talk about how prebuilt binaries could
> be better supported. There was some discussion about how "locked sstate" could
> actually handle this quite neatly. I thought I'd have a look at that and came up
> with a few patches to illustrate what I was talking about.
Interesting, thanks for bringing this up also on mailing list!
How could one implement a variant where source recipe vs. pre-compiled
binary build would be chosen based on access rights to a git tree in
SRC_URI?
Cheers,
-Mikko
next prev parent reply other threads:[~2020-11-02 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 12:53 [PATCH 0/2] Example of how prebuilt binaries and locked sstate could work Richard Purdie
2020-11-01 12:53 ` [PATCH 1/2] sstate: Promote do_install to an sstate test Richard Purdie
2020-11-01 12:53 ` [PATCH 2/2] selftest: Add binaryonly example and selftest Richard Purdie
2020-11-02 9:01 ` Mikko Rapeli [this message]
2020-11-02 10:28 ` [OE-core] [PATCH 0/2] Example of how prebuilt binaries and locked sstate could work Richard Purdie
2020-11-02 11:48 ` Mikko Rapeli
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=20201102090100.GS1246345@korppu \
--to=mikko.rapeli@bmw.de \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=vkraleti@codeaurora.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