From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>,
"meta-virtualization@lists.yoctoproject.org"
<meta-virtualization@lists.yoctoproject.org>
Cc: "adrian.freihofer@gmail.com" <adrian.freihofer@gmail.com>
Subject: use of yocto-cfg-fragments
Date: Thu, 2 Nov 2023 10:24:29 +0000 [thread overview]
Message-ID: <06ec1922fd901a02d492158a995cfbeeb158e379.camel@siemens.com> (raw)
Hello Bruce!
Trying to understand the usage of SRC_URI type=kmeta/kernel-cache in
commits
5c2129118797 ("virtualization/config: allow conditional use of yocto-cfg-fragments")
and 5be8686e659c ("kernel: fix conditional application of fragments").
I have an issue implementing some locally-maintained fragments, I'm adding
"file://features/debug;type=kmeta;destsuffix=features/debug" to SRC_URI in my
kernel recipe derived from kernel-yocto class and this actually works
fine for me until I try to combine this with meta-virtualization.
My current understanding is that
meta-virtualization/recipes-kernel/linux/linux-yocto_virtualization.inc
makes an assumption that any type=kmeta will point to upstream
git://git.yoctoproject.org/yocto-kernel-cache but this doesn't hold
for my use case.
The only type=kmeta is my local file:// storage and the following
linux-yocto_virtualization.inc part leads to fetch failure (fetch
from Internet not expected/forbidden):
# if kernel-yocto has been inherited (how we can check for configuration
# fragment merging suport at the moment, then add a dependency on the
# configuration fragment repository. This allows us to be sure that our
# features can be enabled via the fragments
do_kernel_metadata[depends] += "${@['', 'yocto-cfg-fragments-native:do_populate_sysroot'][(bb.data.inherits_class('kernel-yocto', d))]}"
Summary: 1 task failed:
virtual:native:.../projects/ccp-sd-virt/../../meta-virtualization/recipes-kernel/linux/yocto-cfg-fragments.bb:do_fetch
When I read the comment "if the kernel-yocto meta-data routine automatically
starts to add the recipe-sysroot-native..." I get a feeling that
this feature is still "work in progress". Are there any further developments
I could test in this direction?
What would be a proper resolution of the above type=kmeta usage conflict from
your PoV?
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next reply other threads:[~2023-11-02 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 10:24 Sverdlin, Alexander [this message]
2023-11-02 19:13 ` use of yocto-cfg-fragments Bruce Ashfield
2023-11-03 9:15 ` Sverdlin, Alexander
2023-11-03 12:51 ` Bruce Ashfield
[not found] ` <17941DFC88BEAF3E.3650@lists.yoctoproject.org>
2023-11-03 13:00 ` [meta-virtualization] " Bruce Ashfield
2023-11-03 13:13 ` Sverdlin, Alexander
2023-11-03 13:59 ` Bruce Ashfield
2023-11-03 14:21 ` Sverdlin, Alexander
2023-11-03 14:40 ` Bruce Ashfield
2023-11-06 9:20 ` [PATCH RFC] kernel: allow KERNEL_META_TYPE redefinition A. Sverdlin
2023-11-06 13:41 ` Bruce Ashfield
[not found] ` <17950C6F5A95F7ED.26468@lists.yoctoproject.org>
2023-11-07 0:57 ` [meta-virtualization] " Bruce Ashfield
2023-11-07 10:10 ` Sverdlin, Alexander
2023-11-07 13:23 ` Bruce Ashfield
2023-11-07 13:57 ` Sverdlin, Alexander
2023-11-07 14:11 ` Bruce Ashfield
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=06ec1922fd901a02d492158a995cfbeeb158e379.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=adrian.freihofer@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).