From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lttng-tools: not rrecommend on lttng-modules
Date: Wed, 18 Mar 2026 07:37:20 +0000 [thread overview]
Message-ID: <7029edb75e3d8c609447de0d0f7d9f4e73ec5521.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260302064010.1421315-1-kai.kang@windriver.com>
On Mon, 2026-03-02 at 14:40 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> As in the lttng manual [1]:
>
> Most distributions mark the LTTng-modules and LTTng-UST packages as
> optional when installing LTTng-tools (which is always required). In
> the following sections, we always provide the steps to install all
> three, but note that:
>
> * You only need to install LTTng-modules if you intend to use the
> Linux kernel LTTng tracer.
> * You only need to install LTTng-UST if you intend to use the user
> space LTTng tracer.
>
> there should be no force dependency between lttng-tools and
> lttng-modules. When set lttng-modules in RRECOMMENDS, it always
> forces
> to build lttng-modules whether it is required or not.
>
> Compare to rpm spec [2] and debian conf [3], there are no any
> dependency
> between them too.
>
> So remove the RRECOMMENDS setting.
>
> [1]: https://lttng.org/docs/v2.14/#doc-installing-lttng
> [2]:
> https://rpmfind.net/linux/RPM/fedora/updates/testing/43/aarch64/Packages/l/lttng-tools-2.14.0-4.fc43.aarch64.html
> [3]: https://packages.debian.org/trixie/lttng-tools
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
The removal of the dependency probably makes sense but we need to add
lttng-modules to packagegroup-core-tools-profile instead.
Cheers,
Richard
next prev parent reply other threads:[~2026-03-18 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 6:40 [PATCH] lttng-tools: not rrecommend on lttng-modules kai.kang
2026-03-18 2:08 ` [OE-core] " Kai
2026-03-18 7:37 ` Richard Purdie [this message]
2026-03-18 7:45 ` Kai
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=7029edb75e3d8c609447de0d0f7d9f4e73ec5521.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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