From 3dbb9dfaed3a0a3af9cf1ed5c6c3509472c52a31 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 00:43:50 +0200 Subject: [PATCH 01/15] README.rst: fix markup syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This should be shown as 'code', not as 'italic'. Signed-off-by: Enrico Jörns --- README.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 94656ce..acc2aaa 100644 --- a/README.rst +++ b/README.rst @@ -97,7 +97,7 @@ III. Adding the RAUC Update Service to Your Device To prepare your device for using RAUC as its update handler, you have to follow at least the following steps: -1. Add `rauc` to `DISTRO_FEATURES` in your distro (or local) config:: +1. Add ``rauc`` to ``DISTRO_FEATURES`` in your distro (or local) config:: DISTRO_FEATURES += "rauc" @@ -109,7 +109,7 @@ you have to follow at least the following steps: FILESEXTRAPATHS:prepend := "${THISDIR}/files:" 3. Create a bundle recipe for your device by adding a recipe - that inherits the `bundle` class and adds all desired + that inherits the ``bundle`` class and adds all desired configuration:: inherit bundle @@ -131,7 +131,7 @@ you have to follow at least the following steps: bitbake my-bundle-recipe Note: If you do not use packagegroup-base, you als need to manually add -the `rauc` package to your systems image recipe:: +the ``rauc`` package to your systems image recipe:: IMAGE_INSTALL:append = " rauc" From 3a7fa4e21b302cb9c1105f50cefb4f3550e026af Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 12:50:37 +0200 Subject: [PATCH 02/15] README.rst: minor wording and typo fixes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Enrico Jörns --- README.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.rst b/README.rst index acc2aaa..ead9e95 100644 --- a/README.rst +++ b/README.rst @@ -95,7 +95,7 @@ III. Adding the RAUC Update Service to Your Device ================================================== To prepare your device for using RAUC as its update handler, -you have to follow at least the following steps: +at least the following steps are required: 1. Add ``rauc`` to ``DISTRO_FEATURES`` in your distro (or local) config:: @@ -130,7 +130,7 @@ you have to follow at least the following steps: bitbake my-bundle-recipe -Note: If you do not use packagegroup-base, you als need to manually add +Note: If you do not use packagegroup-base, you also need to manually add the ``rauc`` package to your systems image recipe:: IMAGE_INSTALL:append = " rauc" @@ -149,7 +149,7 @@ To use ``rauc-hawkbit-updater`` in your system add to your image recipe:: V. Configure Custom Kernel ========================== -In order to use RAUC on your system, the kernel must support SquashFS and loop +To use RAUC on your system, the kernel must support SquashFS and loop mounts. For the standard yocto kernel, the meta-rauc layer provides a kernel configuration fragment that enables the config options required for this. @@ -181,7 +181,7 @@ VII. Contributing To report bugs, file a new `issue `_ on GitHub. -For fixing bugs, bumping recipes or adding new features, open a `pull request +For fixing bugs, bumping recipes, or adding new features, open a `pull request `_ on GitHub. Add a ``Signed-off-by`` line to your commits according to the From b70792afbb38e5d0bed1cdd2a5f25836a627f924 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 12:27:05 +0200 Subject: [PATCH 03/15] README.rst: fix rauc-hawkbit-updater section heading MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This plural form originates from when the section described rauc-hawkbit, too. Fixes: 1a9a22d8 ("rauc-hawkbit: remove recipe and references") Signed-off-by: Enrico Jörns --- README.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index ead9e95..2121787 100644 --- a/README.rst +++ b/README.rst @@ -136,8 +136,8 @@ the ``rauc`` package to your systems image recipe:: IMAGE_INSTALL:append = " rauc" -IV. Building The RAUC hawkBit Clients -===================================== +IV. Building The RAUC hawkBit Client +==================================== This layer offers support for ``rauc-hawkbit-updater``, a daemon that interfaces between RAUC and the hawkBit deployment server. From dff0efe4e41917be2a97a5413444a2fc051b1bb2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 01:04:18 +0200 Subject: [PATCH 04/15] README.rst: drop generic 'Adding the rauc Layer..' chapter MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is basic Yocto/OE knowledge that is not worth being replicated in each individual layer. While at it, drop the section numbers, since we don't intend to write a whole book here. Signed-off-by: Enrico Jörns --- README.rst | 47 ++++++++++++++--------------------------------- 1 file changed, 14 insertions(+), 33 deletions(-) diff --git a/README.rst b/README.rst index 2121787..ed8a047 100644 --- a/README.rst +++ b/README.rst @@ -58,27 +58,8 @@ configuration-specific adaptions from your ``rauc_%.bbappend`` to a ``rauc-conf.bbappend`` file. -I. Adding the rauc Layer to Your Build -====================================== - -In order to use this layer, you need to make the build system aware of -it. - -Assuming the rauc layer exists at the top-level of your -yocto build tree, you can add it to the build system by adding the -location of the rauc layer to bblayers.conf, along with any -other layers needed. e.g.:: - - BBLAYERS ?= " \ - /path/to/yocto/meta \ - /path/to/yocto/meta-poky \ - /path/to/yocto/meta-yocto-bsp \ - /path/to/yocto/meta-rauc \ - " - - -II. Building and Using RAUC Host Tool -===================================== +Building and Using RAUC Host Tool +================================= If you intend to build and use RAUC as a host tool from your BSP, e.g. for calling ``rauc info`` on your built bundle, simply run:: @@ -91,8 +72,8 @@ If you need to execute the ``casync`` host tool manually, you can do this by run bitbake casync-native -caddto_recipe_sysroot oe-run-native casync-native casync --help -III. Adding the RAUC Update Service to Your Device -================================================== +Adding the RAUC Update Service to Your Device +============================================= To prepare your device for using RAUC as its update handler, at least the following steps are required: @@ -136,8 +117,8 @@ the ``rauc`` package to your systems image recipe:: IMAGE_INSTALL:append = " rauc" -IV. Building The RAUC hawkBit Client -==================================== +Building The RAUC hawkBit Client +================================ This layer offers support for ``rauc-hawkbit-updater``, a daemon that interfaces between RAUC and the hawkBit deployment server. @@ -146,8 +127,8 @@ To use ``rauc-hawkbit-updater`` in your system add to your image recipe:: IMAGE_INSTALL:append = " rauc-hawkbit-updater" -V. Configure Custom Kernel -========================== +Configure Custom Kernel +======================= To use RAUC on your system, the kernel must support SquashFS and loop mounts. For the standard yocto kernel, the meta-rauc layer provides a kernel @@ -157,8 +138,8 @@ If you build your own kernel with a full custom ``defconfig`` file, you have to make sure that the options in ``recipes-kernel/linux/linux-yocto/rauc.cfg`` are enabled in your configuration, too. -VI. Build RAUC Development Version -================================== +Build RAUC Development Version +============================== Beside the standard release version recipes, the _git variants of RAUC recipes allow to build RAUC from a master branch revision that is newer than the latest @@ -175,8 +156,8 @@ in your local.conf. Note that this has the same effect as setting ``DEFAULT_PREFERENCE = "1"`` for each recipe (target/native/nativesdk) individually. -VII. Contributing -================= +Contributing +============ To report bugs, file a new `issue `_ on GitHub. @@ -206,8 +187,8 @@ When using git, this can be done automatically with:: Note that backports will be accepted for actively maintained `poky releases `_ only! -VIII. References -================ +References +========== .. [1] http://rauc.readthedocs.io/en/latest/ From b89a28f4b79a3fd78c4cd4bf55770afe8b7e4072 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 12:06:12 +0200 Subject: [PATCH 05/15] README.rst: rewrite introduction text MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Better outline the purpose of RAUC and this layer. Add note on host and target side integration. Signed-off-by: Enrico Jörns --- README.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index ed8a047..ee2ea81 100644 --- a/README.rst +++ b/README.rst @@ -12,10 +12,13 @@ |MIT| |Matrix| -The meta-rauc layer provides support for integrating the RAUC update tool -into your device. +The meta-rauc Yocto/OpenEmbedded layer provides integration for +`RAUC `_, a robust and secure **update framework +for embedded Linux systems**. + +This layer integrates RAUC into Yocto builds for both **target usage (update +client)** and **host usage (bundle creation)**. -Please see the corresponding sections below for more information. For a detailed description on steps necessary to integrate RAUC into your project, refer https://rauc.readthedocs.io/en/latest/integration.html. From 55f8b2302618f2b39100840e60211e7c21f38059 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 01:15:07 +0200 Subject: [PATCH 06/15] README.rst: simplify (layer) dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Shorten the description * drop 'bitbake', which of course is required, but not a layer. * clarify the casync requirements and scope Signed-off-by: Enrico Jörns --- README.rst | 19 ++++++------------- 1 file changed, 6 insertions(+), 13 deletions(-) diff --git a/README.rst b/README.rst index ee2ea81..af9bcea 100644 --- a/README.rst +++ b/README.rst @@ -23,23 +23,16 @@ For a detailed description on steps necessary to integrate RAUC into your project, refer https://rauc.readthedocs.io/en/latest/integration.html. -Dependencies -============ - -This layer depends on:: +Layer Dependencies +================== - URI: https://github.com/openembedded/bitbake.git - branch: master +This layer depends on: - URI: https://github.com/openembedded/openembedded-core.git - layers: meta - branch: master +* `openembedded-core `_ -For fuse-support in casync (the default):: +To use the optional casync feature with FUSE, you will also need: - URI: https://github.com/openembedded/meta-openembedded.git - layers: meta-filesystems - branch: master +* ``meta-filesystems`` from `meta-openembedded `_. Patches ======= From 9a07bf7536f4c0e40f8a122b0339f56ca06a4252 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 11:15:15 +0200 Subject: [PATCH 07/15] README.rst: clarify some aspects for backporting MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * 'changes' is too broad, we don't intend to backport all new features * allow 'backport' in backport notes, too (e.g. when not doing a pure cherry pick * replace 'poky releases' by 'Yocto releases' Signed-off-by: Enrico Jörns --- README.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index af9bcea..5c23556 100644 --- a/README.rst +++ b/README.rst @@ -168,19 +168,19 @@ Add a ``Signed-off-by`` line to your commits according to the Backporting ----------- -For backporting changes to a stable or LTS branch, two options exist: +For backporting fixes or version bumps to a stable or LTS branch, two options exist: a) drop a backport request in the original pull request b) backport on your own and create a new pull request -When doing backports on your own, make sure to include a cherry-pick note and +When doing backports on your own, make sure to include a cherry-pick/backport note and the original commit-ish in a line below the original Signed-off-by and add your own Signed-off-by below. When using git, this can be done automatically with:: git cherry-pick -xs -Note that backports will be accepted for actively maintained `poky releases +Note that backports will be accepted for `actively maintained Yocto releases `_ only! References From f4e6d581d851f8d07c9055ed0b1ee6ee9c1c719f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 11:18:36 +0200 Subject: [PATCH 08/15] README:rst: drop redundant "Patches" chapter MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This mainly replicates the information from the "Contributing" chapter. Move the Maintainers note there. Signed-off-by: Enrico Jörns --- README.rst | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index 5c23556..db24e34 100644 --- a/README.rst +++ b/README.rst @@ -34,13 +34,6 @@ To use the optional casync feature with FUSE, you will also need: * ``meta-filesystems`` from `meta-openembedded `_. -Patches -======= - -Please submit patches via GitHub pull request on https://github.com/rauc/meta-rauc - -Maintainer: Enrico Joerns - Migration Notes =============== @@ -183,6 +176,11 @@ When using git, this can be done automatically with:: Note that backports will be accepted for `actively maintained Yocto releases `_ only! +Maintainer(s) +------------- + +* Enrico Joerns + References ========== From a5aeeb2cdf14fde505f9bac27622af4a03451132 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 11:47:12 +0200 Subject: [PATCH 09/15] README.rst: improve wording for rauc-conf.bbappend instructions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It's not sufficient to just set FILESEXTRAPATHS, you'd also need the system.conf file itself. Also the keyring is installed this way for most use cases. Reword 'RAUC update file' to 'RAUC system configuration' which is more appropriate. Signed-off-by: Enrico Jörns --- README.rst | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/README.rst b/README.rst index db24e34..6ee51a5 100644 --- a/README.rst +++ b/README.rst @@ -71,13 +71,18 @@ at least the following steps are required: DISTRO_FEATURES += "rauc" -2. Add a ``rauc-conf.bbappend`` in your device-specific (BSP) layer - that installs your RAUC system configuration file under - ``/etc/rauc/system.conf``. For information on how to write the RAUC - update file, please refer to the RAUC user documentation [1]_:: +2. Provide a RAUC system configuration (and keyring) in your BSP layer by + creating a ``rauc-conf.bbappend`` that fetches your custom ``system.conf`` + (and keyring) from your layer:: FILESEXTRAPATHS:prepend := "${THISDIR}/files:" + The ``rauc-conf`` recipe will install these files into ``/etc/rauc/`` by + default. + + For information on how to write a proper RAUC system configuration, please + refer to the RAUC user documentation [1]_. + 3. Create a bundle recipe for your device by adding a recipe that inherits the ``bundle`` class and adds all desired configuration:: From 2adfd241886ee870385a34ea6289d0efea37218f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 11:54:16 +0200 Subject: [PATCH 10/15] README.rst: add verity format to example MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Recent bundles should not be build without, if possible. Signed-off-by: Enrico Jörns --- README.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.rst b/README.rst index 6ee51a5..4bc0449 100644 --- a/README.rst +++ b/README.rst @@ -89,6 +89,8 @@ at least the following steps are required: inherit bundle + RAUC_BUNDLE_FORMAT = "verity" + RAUC_BUNDLE_SLOTS = "rootfs" RAUC_SLOT_rootfs = "my-rootfs-recipe" From 801225f85418482dc460ecc667571e363953cdee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Thu, 16 Apr 2026 08:52:18 +0200 Subject: [PATCH 11/15] README.rst: simplify and align host tool chapter MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * add missing 'the' to heading * remove useless 'if you intend' * point out 'manually' usage of the RAUC tool * shorten and align wording Signed-off-by: Enrico Jörns --- README.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.rst b/README.rst index 4bc0449..1d2e7b3 100644 --- a/README.rst +++ b/README.rst @@ -47,16 +47,16 @@ configuration-specific adaptions from your ``rauc_%.bbappend`` to a ``rauc-conf.bbappend`` file. -Building and Using RAUC Host Tool -================================= +Building and Using the RAUC Host Tool +===================================== -If you intend to build and use RAUC as a host tool from your BSP, e.g. for -calling ``rauc info`` on your built bundle, simply run:: +To manually build and use RAUC as a host tool from your BSP (e.g. for +calling ``rauc info`` on your built bundle), run:: bitbake rauc-native -caddto_recipe_sysroot oe-run-native rauc-native rauc info --keyring=/path/to/keyring.pem tmp/deploy/images//.raucb -If you need to execute the ``casync`` host tool manually, you can do this by running:: +To manually build and use the ``casync`` host tool, run:: bitbake casync-native -caddto_recipe_sysroot oe-run-native casync-native casync --help From c177fac93fb5145056126ec01965292dc2260fd2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Thu, 16 Apr 2026 09:03:28 +0200 Subject: [PATCH 12/15] README.rst: move host tool chapter after target integration MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Using RAUC manually as a host tool is less important than integrating it for the target. Signed-off-by: Enrico Jörns --- README.rst | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/README.rst b/README.rst index 1d2e7b3..2099d26 100644 --- a/README.rst +++ b/README.rst @@ -47,20 +47,6 @@ configuration-specific adaptions from your ``rauc_%.bbappend`` to a ``rauc-conf.bbappend`` file. -Building and Using the RAUC Host Tool -===================================== - -To manually build and use RAUC as a host tool from your BSP (e.g. for -calling ``rauc info`` on your built bundle), run:: - - bitbake rauc-native -caddto_recipe_sysroot - oe-run-native rauc-native rauc info --keyring=/path/to/keyring.pem tmp/deploy/images//.raucb - -To manually build and use the ``casync`` host tool, run:: - - bitbake casync-native -caddto_recipe_sysroot - oe-run-native casync-native casync --help - Adding the RAUC Update Service to Your Device ============================================= @@ -113,6 +99,20 @@ the ``rauc`` package to your systems image recipe:: IMAGE_INSTALL:append = " rauc" +Building and Using the RAUC Host Tool +===================================== + +To manually build and use RAUC as a host tool from your BSP (e.g. for +calling ``rauc info`` on your built bundle), run:: + + bitbake rauc-native -caddto_recipe_sysroot + oe-run-native rauc-native rauc info --keyring=/path/to/keyring.pem tmp/deploy/images//.raucb + +To manually build and use the ``casync`` host tool, run:: + + bitbake casync-native -caddto_recipe_sysroot + oe-run-native casync-native casync --help + Building The RAUC hawkBit Client ================================ From 562ecbdb363f6f8fea6c8eec64a48d5f5b6ab842 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Thu, 16 Apr 2026 09:06:05 +0200 Subject: [PATCH 13/15] README.rst: split target configuration from bundle building MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This was mixed in the same chapter and could easily be overlooked, since the heading just noted "Adding the RAUC Update Service to Your Device". Signed-off-by: Enrico Jörns --- README.rst | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index 2099d26..d2fad06 100644 --- a/README.rst +++ b/README.rst @@ -69,7 +69,15 @@ at least the following steps are required: For information on how to write a proper RAUC system configuration, please refer to the RAUC user documentation [1]_. -3. Create a bundle recipe for your device by adding a recipe +Note: If you do not use packagegroup-base, you also need to manually add +the ``rauc`` package to your systems image recipe:: + + IMAGE_INSTALL:append = " rauc" + +Building a RAUC Update Bundle +============================= + +1. Create a bundle recipe for your device by adding a recipe that inherits the ``bundle`` class and adds all desired configuration:: @@ -89,15 +97,10 @@ at least the following steps are required: For a more detailed explanation on the required and available variables, read the notes in the bundle.bbclass file. -4. Build a bundle and the rootfs for your device:: +2. Build a bundle and the rootfs for your device:: bitbake my-bundle-recipe -Note: If you do not use packagegroup-base, you also need to manually add -the ``rauc`` package to your systems image recipe:: - - IMAGE_INSTALL:append = " rauc" - Building and Using the RAUC Host Tool ===================================== From e6577cfc2c8ef8bded5e2b1988cae2a44be04266 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 11:56:35 +0200 Subject: [PATCH 14/15] README.rst: add a note on the layer's release cycle MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Enrico Jörns --- README.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.rst b/README.rst index d2fad06..9b38914 100644 --- a/README.rst +++ b/README.rst @@ -155,6 +155,14 @@ in your local.conf. Note that this has the same effect as setting ``DEFAULT_PREFERENCE = "1"`` for each recipe (target/native/nativesdk) individually. +Release Cycle +============= + +We follow the Yocto Project release methodology, schedule, and stable/LTS +support timelines. +See https://docs.yoctoproject.org/ref-manual/release-process.html for more +information. + Contributing ============ From af36ac0db1b9efd851c7ed9c3672ff560ab9c37c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Enrico=20J=C3=B6rns?= Date: Wed, 8 Apr 2026 01:06:31 +0200 Subject: [PATCH 15/15] rauc: prepare for hermetic /usr/ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The /etc directory is meant for 'local administrator' usage, which a distro build by OE isn't. For the same reason, several OE upstream packages (including systemd itself) already switch to installing into /usr instead of /etc. For details on the concept, see [1]. RAUC supports reading the system.conf from /usr/ since v1.13 [2]. For the next Yocto LTS release, we adapt to the new installation location, which might require migration for existing integrations. However, for most cases, no manual change should be required. Add a note to the migration chapter to make users ware of this. [1] https://0pointer.net/blog/fitting-everything-together.html [2] https://github.com/rauc/rauc/pull/1557 Partly based on 4cb7c476 ("rauc: prepare support for locating the config in /usr or /run"). Signed-off-by: Enrico Jörns --- README.rst | 6 +++++- recipes-core/rauc/files/system.conf | 6 +++--- recipes-core/rauc/rauc-conf.bb | 10 ++++++---- 3 files changed, 14 insertions(+), 8 deletions(-) diff --git a/README.rst b/README.rst index 9b38914..21ad965 100644 --- a/README.rst +++ b/README.rst @@ -37,6 +37,10 @@ To use the optional casync feature with FUSE, you will also need: Migration Notes =============== +Since **wrynose**, the ``system.conf`` and keyring file will be installed into +``/usr/lib/rauc`` by default to align with the 'hermetic ``/usr/``' policy +followed by other OE components (like systemd), too. + Since **scarthgap**, the platform configuration (system.conf, keyring, etc.) was moved to a separate ``rauc-conf.bb`` recipe to allow building the rauc package with ``TUNE_PKGARCH`` and have a clearer separation between the binary and the @@ -63,7 +67,7 @@ at least the following steps are required: FILESEXTRAPATHS:prepend := "${THISDIR}/files:" - The ``rauc-conf`` recipe will install these files into ``/etc/rauc/`` by + The ``rauc-conf`` recipe will install these files into ``/usr/lib/rauc/`` by default. For information on how to write a proper RAUC system configuration, please diff --git a/recipes-core/rauc/files/system.conf b/recipes-core/rauc/files/system.conf index 6164143..966ee17 100644 --- a/recipes-core/rauc/files/system.conf +++ b/recipes-core/rauc/files/system.conf @@ -1,6 +1,6 @@ -## This is an example RAUC system configuration. This file will be installed -## into /etc/rauc/system.conf on your target and describes your system from the -## perspective of the RAUC update service. +## This is an example RAUC system configuration. This file will be be looked up +## in {/etc,/run,/usr/lib}/rauc/system.conf on your target and describes your +## system from the perspective of the RAUC update service. ## ## Adapt and extend the below configuration to your needs and place it in the ## BSP layer of you project. Create a rauc .bbappend file that adds this file diff --git a/recipes-core/rauc/rauc-conf.bb b/recipes-core/rauc/rauc-conf.bb index 0e829ec..a6048c6 100644 --- a/recipes-core/rauc/rauc-conf.bb +++ b/recipes-core/rauc/rauc-conf.bb @@ -22,13 +22,15 @@ do_install () { if ! grep -q "^[^#]" ${UNPACKDIR}/system.conf; then bbwarn "Please overwrite example system.conf with a project specific one!" fi - install -d ${D}${sysconfdir}/rauc - install -m 0644 ${UNPACKDIR}/system.conf ${D}${sysconfdir}/rauc/ + install -d ${D}${nonarch_libdir}/rauc + install -m 0644 ${UNPACKDIR}/system.conf ${D}${nonarch_libdir}/rauc/ # Warn if CA file was not overwritten if ! grep -q "^[^#]" ${UNPACKDIR}/${RAUC_KEYRING_FILE}; then bbwarn "Please overwrite example ca.cert.pem with a project specific one, or set the RAUC_KEYRING_FILE variable with your file!" fi - install -d ${D}${sysconfdir}/rauc - install -m 0644 ${UNPACKDIR}/${RAUC_KEYRING_FILE} ${D}${sysconfdir}/rauc/ + install -d ${D}${nonarch_libdir}/rauc + install -m 0644 ${UNPACKDIR}/${RAUC_KEYRING_FILE} ${D}${nonarch_libdir}/rauc/ } + +FILES:${PN} += "${nonarch_libdir}/rauc"