migration-guides: systemd.bbclass do not add Also services for 5.2

Covers the changes introduced by commit
https://git.yoctoproject.org/poky/commit/?id=efa5f65c2214239ed7aaf7bd8998683e755c5660

(From yocto-docs rev: 71acf03e02d1e21a4dbe081e75d1e4383ac2f3ac)

Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Adrian Freihofer 2025-01-17 17:11:41 +01:00 committed by Richard Purdie
parent 51ffd381e3
commit 9c2268e92b

View File

@ -74,6 +74,26 @@ systemd changes
As a consequence, the ``systemd`` recipe no longer contains the ``usrmerge``
:term:`PACKAGECONFIG` option as it is now implied by default.
- ``systemd.bbclass``: If a ``systemd`` service file had referred to other service
files by starting them via
`Also <https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#Also=>`__,
the other service files were automatically added to the :term:`FILES` variable of
the same package. Example:
a.service contains::
[Install]
Also=b.service
If ``a.service`` is packaged in package ``A``, ``b.service`` was
automatically packaged into package ``A`` as well. This happened even if
``b.service`` was explicitly added to package ``B`` using :term:`FILES` and
:term:`SYSTEMD_SERVICE` variables.
This prevented such services from being packaged into different packages.
Therefore, this automatic behavior has been removed for service files (but
not for socket files).
Now all service files must be explicitly added to :term:`FILES`.
Recipe changes
~~~~~~~~~~~~~~