d876cfc5bf
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 <richard.purdie@linuxfoundation.org>
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 <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
||
|---|---|---|
| .. | ||
| singularity | ||
| README | ||
| singularity_git.bb | ||
Singularity is a container platform based on the principle of mobility of compute, and it is designed for use within HPC clusters. For more info see singularity.lbl.gov.
To test whether the software functions correctly, you can use singularity selftest. This is what you would expect to see:
~# singularity selftest
- sh -c test -f /etc/singularity/singularity.conf (retval=0) OK
- test -u /usr/libexec/singularity/bin/action-suid (retval=0) OK
- test -u /usr/libexec/singularity/bin/create-suid (retval=0) OK
- test -u /usr/libexec/singularity/bin/expand-suid (retval=0) OK
- test -u /usr/libexec/singularity/bin/export-suid (retval=0) OK
- test -u /usr/libexec/singularity/bin/import-suid (retval=0) OK
- test -u /usr/libexec/singularity/bin/mount-suid (retval=0) OK
You can also pull a container from Docker Hub to prove full functionality (Test was performed on a Raspberry Pi 3, hence the arm32v7 part of the Docker link. Make sure you pull an image which is compatible with your hardware.) For instance:
~# singularity pull docker://arm32v7/debian:latest Initializing Singularity image subsystem Opening image file: debian-latest.img Creating 200MiB image Binding image to loop Creating file system within image Image is done: debian-latest.img Docker image path: index.docker.io/arm32v7/debian:latest Cache folder set to /home/root/.singularity/docker [1/1] |===================================| 100.0% Importing: base Singularity environment Importing: /home/root/.singularity/docker/sha256:ed4f1f0d0a0457e7f76ffb25a8d6a193007709dd312b7647cb44fc6979ec4a53.tar.gz Importing: /home/root/.singularity/metadata/sha256:89997b2c16b29c5a3a316e314172ef21b36f67cc3200b1c4d95927f716dbee83.tar.gz Done. Container is at: debian-latest.img ~# singularity shell debian-latest.img Singularity: Invoking an interactive shell within container...
Singularity debian-latest.img:~> echo "Hello from within the container!" Hello from within the container! Singularity debian-latest.img:~> ls / bin dev home lost+found mnt proc run singularity sys usr boot etc lib media opt root sbin srv tmp var Singularity debian-latest.img:~> exit exit ~#