From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@gmail.com>, <docs@lists.yoctoproject.org>
Cc: "Adrian Freihofer" <adrian.freihofer@siemens.com>
Subject: Re: [docs] [PATCH 1/3] migration-guides: systemd.bbclass do not add Also services for 5.2
Date: Thu, 26 Dec 2024 09:35:31 +0100 [thread overview]
Message-ID: <D6LHTIGUQE41.2Q8LEC1YVJV0Y@bootlin.com> (raw)
In-Reply-To: <20241224140251.24389-2-adrian.freihofer@siemens.com>
Hi Adrian,
Thanks for the update on this! Here below are some suggestions.
On Tue Dec 24, 2024 at 3:02 PM CET, Adrian Freihofer via lists.yoctoproject.org wrote:
> Covers the chagnes introduced by commit
> https://git.yoctoproject.org/poky/commit/?id=efa5f65c2214239ed7aaf7bd8998683e755c5660
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
> .../migration-guides/migration-5.2.rst | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
> index cb70e19da..2ae8e73a7 100644
> --- a/documentation/migration-guides/migration-5.2.rst
> +++ b/documentation/migration-guides/migration-5.2.rst
> @@ -74,6 +74,25 @@ 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 as “Also”, the other service files were automatically added
s/by starting them as/with/?
s/“Also”/`Also <https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#Also=>`__/?
> + to the ``FILES`` variable of the same package. Example:
s/``FILES``/:term:`FILES`/
Same for FILES and SYSTEMD_SERVICE below.
> +
> + a.service contains:
Nitpick:
s/contains:/contains::/
and remove ".. code-block:: ini" below
> +
> + .. code-block:: ini
> +
> + [Install]
> + Also=b.service
> +
> + If a.service is packed in package A, b.service is automatically packed
s/packed/packaged/
> + into package A as well. This happens even if b.service is explicitly
> + added to package B using FILES and SYSTEMD_SERVICE variables.
> +
> + This prevents such services from being packaged into different packages.
> + Therefore, this automatic has been removed for service files (but not for socket files).
"automatic behavior"?
> + Now all service files must be explicitly added to ``FILES``.
> +
> Recipe changes
> ~~~~~~~~~~~~~~
>
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-12-26 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 14:02 [PATCH 0/3] Cover systemd.bbclass and devtool ide-sdk changes Adrian Freihofer
2024-12-24 14:02 ` [PATCH 1/3] migration-guides: systemd.bbclass do not add Also services for 5.2 Adrian Freihofer
2024-12-26 8:35 ` Antonin Godard [this message]
2025-01-13 16:09 ` [docs] " Quentin Schulz
2024-12-24 14:02 ` [PATCH 2/3] sdk-manual: extensible.rst: update devtool ide-sdk Adrian Freihofer
2024-12-26 8:35 ` [docs] " Antonin Godard
2024-12-24 14:02 ` [PATCH 3/3] sdk-manual: extensible.rst: remove confusing post-install-logging Adrian Freihofer
2024-12-26 8:35 ` [docs] " Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D6LHTIGUQE41.2Q8LEC1YVJV0Y@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=adrian.freihofer@gmail.com \
--cc=adrian.freihofer@siemens.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox