mbox series

[0/5] systemd split networkd package

Message ID 20241211215859.2187259-1-adrian.freihofer@gmail.com
Headers show
Series systemd split networkd package | expand

Message

Adrian Freihofer Dec. 11, 2024, 9:58 p.m. UTC 
First of all, this patch series fixes a bug in systemd.bbclass that
forces service files with an Also= relationship to be in the same
package. This may often be the case, but as long as the RDEPENDS
between the packages are set correctly, it is no problem to distribute
the service files over several packages.

If service files referenced with Also= are no longer automatically added
to the list of FILES, build errors caused by unpacked files are
expected. A bitbake world has shown that there are only two recipes in
oe-core that use automatic packing: busybox and dropbear. There are 2
patches that fix this.

Also= relation are probably most often used for sockets. Consequently
the systemd.bbclass should also allow to split socket files into
separate packages. However, that's proably practically not used and
would cause tons of packaging errors. Therefore the automatic packaging
feature for sockets is not changed.

The latest patch splits systemd-networkd into its own package. This adds
a little extra complexity, but splitting systemd into packages is a good
step towards making Yocto more usable in binary form.

Adrian Freihofer (5):
  busybox: add klogd service to FILES
  dropbear: add dropbearkey.service to FILES
  systemd.bbclass: refactor adding files
  systemd.bbclass: do not automatically add Also services
  systemd: split networkd into its own package

 meta/classes-recipe/systemd.bbclass           | 28 ++++++++-----------
 meta/recipes-core/busybox/busybox.inc         |  9 +++++-
 .../recipes-core/dropbear/dropbear_2024.86.bb |  2 ++
 meta/recipes-core/systemd/systemd_256.8.bb    | 27 ++++++++++++++++--
 4 files changed, 46 insertions(+), 20 deletions(-)