From: Quentin Schulz <quentin.schulz@cherry.de>
To: adrian.freihofer@gmail.com, docs@lists.yoctoproject.org
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>
Subject: Re: [docs] [PATCH v2 1/3] migration-guides: systemd.bbclass do not add Also services for 5.2
Date: Mon, 13 Jan 2025 18:21:39 +0100 [thread overview]
Message-ID: <3a811ecf-d2ee-4389-bd50-0ffe8a1a6d94@cherry.de> (raw)
In-Reply-To: <20250109222015.12658-2-adrian.freihofer@siemens.com>
Hi Adrian,
On 1/9/25 11:17 PM, 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..b18ae30d9 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
``systemd`` ?
> + files by starting them as
> + `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 is automatically packaged
> + into package A as well. This happens even if b.service is explicitly added
> + to package B using FILES and :term:`SYSTEMD_SERVICE` variables.
s/FILES/:term:`FILES`/
For all the above, probably ``a.service``, ``A``, ``b.service``, ``B``,
for words that aren't English.
Looks good otherwise.
Cheers,
Quentin
next prev parent reply other threads:[~2025-01-13 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 22:17 [PATCH v2 0/3] Cover systemd.bbclass and devtool ide-sdk changes Adrian Freihofer
2025-01-09 22:17 ` [PATCH v2 1/3] migration-guides: systemd.bbclass do not add Also services for 5.2 Adrian Freihofer
2025-01-10 9:23 ` [docs] " Antonin Godard
2025-01-13 17:21 ` Quentin Schulz [this message]
2025-01-09 22:17 ` [PATCH v2 2/3] sdk-manual: extensible.rst: update devtool ide-sdk Adrian Freihofer
2025-01-09 22:17 ` [PATCH v2 3/3] sdk-manual: extensible.rst: remove confusing post-install-logging Adrian Freihofer
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=3a811ecf-d2ee-4389-bd50-0ffe8a1a6d94@cherry.de \
--to=quentin.schulz@cherry.de \
--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