linux/meta-virtualization.git/recipes-core/runx, branch master

runx, go-build: mark as deprecated in favor of vxn

2026-02-26T01:05:01+00:00

Update SUMMARY and DESCRIPTION to note that runx is unmaintained (upstream dormant since 2022) and that vxn provides the same Xen DomU container functionality with pluggable hypervisor backends. go-build is the serial FD handler companion to runx and is similarly superseded. Signed-off-by: Bruce Ashfield

core: adjust to OE-core UNPACKDIR changes

2025-06-26T02:53:19+00:00

Adjusting our core recipes to work with the OE core source handling. Note: some of these recipes don't work at runtime, but this makes them parse. These changes are explicit S assignment removal and replacement of WORKDIR with UNPACKDIR. Signed-off-by: Bruce Ashfield

metadata: add whitespace around assignments

2025-04-03T17:56:53+00:00

With: https://lists.openembedded.org/g/bitbake-devel/message/17508 there are many WARNINGs from this layer will cover src_uri.inc files in next commit. Signed-off-by: Martin Jansa Signed-off-by: Bruce Ashfield

treewide: bulk update patches with status field

2023-01-27T15:32:06+00:00

While the insane.bbclass upstream-status check hasn't been made default, users of meta-virtualization may have it enabled in their distros .. so the effect is the same. We must have this tracking tag in out patches. This is a bulk update to add the tag and silence the QA message. As packages get updated, the normal/routine process of checking the patches will continue, and the status fields may (or may not) get more useful. Signed-off-by: Bruce Ashfield

global: convert github SRC_URIs to use https protocol

2021-11-02T13:57:03+00:00

github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

runx: update to v1.0

2021-03-26T15:12:29+00:00

bumping runX to the 1.0 tag - drop patches that are part of the release - bump kernel to v5.4.104 to work with our gcc10 - tweak initrd install to use externally provided busybox Signed-off-by: Bruce Ashfield

runx: allow internal and external busybox

2020-09-22T19:51:27+00:00

runx knows how to build its own copy of busybox for its initrd, adding a flag to allow us to select which mode we want. Signed-off-by: Bruce Ashfield Signed-off-by: Bruce Ashfield

runx: robustness changes

2020-09-22T19:51:17+00:00

Adding one build and one runtime robustness change: - build: specify the syroot native as a library path to qemu user. This allows us to run dynamic executables - runtime: add a patch to increase the serial fd timeout. We'll drop this once it is merged upstream. Signed-off-by: Bruce Ashfield Signed-off-by: Bruce Ashfield

runx: add additional dependencies

2020-09-22T19:50:59+00:00

There are some missing dependencies for a fully functional runx host. We add them here. Signed-off-by: Bruce Ashfield Signed-off-by: Bruce Ashfield