From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Isaac True <itrue@emlix.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/2] linux-custom: add linux-tools package and build perf
Date: Thu, 27 Nov 2025 08:22:07 +0100 [thread overview]
Message-ID: <5a07dd76-3d55-4f02-841a-853f23b8c31c@siemens.com> (raw)
In-Reply-To: <20251126130534.3484253-3-itrue@emlix.com>
On 26.11.25 14:02, 'Isaac True' via isar-users wrote:
> Add an additional package to the linux-custom recipe which can be used
> to deliver tools built from the kernel sources.
>
> Additionally, build the perf tool as part of the kernel build process
> and add it to the linux-tools package, allowing users to install it to
> their target rootfs.
>
> Signed-off-by: Isaac True <itrue@emlix.com>
> ---
> meta/recipes-kernel/linux/files/debian/control.tmpl | 10 ++++++++++
> meta/recipes-kernel/linux/files/debian/isar/build.tmpl | 3 +++
> .../recipes-kernel/linux/files/debian/isar/common.tmpl | 2 ++
> .../linux/files/debian/isar/install.tmpl | 7 +++++++
> meta/recipes-kernel/linux/files/debian/rules.tmpl | 2 +-
> meta/recipes-kernel/linux/linux-custom.inc | 10 ++++++++++
> 6 files changed, 33 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index ee87cf92..edb3960a 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -69,3 +69,13 @@ Conflicts: linux-kbuild-${KERNEL_NAME_PROVIDED}
> Description: ${KERNEL_NAME_PROVIDED} Linux kbuild scripts and tools for @KR@
> This package provides kernel kbuild scripts and tools for @KR@
> This is useful for people who need to build external modules
> +
> +Package: linux-tools-${KERNEL_NAME_PROVIDED}
> +Build-Profiles: <pkg.${BPN}.kernel pkg.${BPN}.tools>
> +Architecture: any
> +Multi-Arch: foreign
> +Depends: ${misc:Depends}, ${shlib:Depends}
> +Description: ${KERNEL_NAME_PROVIDED} Linux tools for @KR@
> + This package provides kernel tools for @KR@.
> + .
> + This is useful for people who want to run things like perf.
Ok, now we have a build profile, that's good. But you are diverting from
how upstream Debian packages the tools - why? Just like linux-libc-dev,
linux-perf etc. should be modelled to be replacements of the original
packages. Also reuse upstream descriptions then.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/5a07dd76-3d55-4f02-841a-853f23b8c31c%40siemens.com.
next prev parent reply other threads:[~2025-11-27 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 13:02 [PATCH v2 0/2] linux-custom: add linux-tools package and perf 'Isaac True' via isar-users
2025-11-26 13:02 ` [PATCH v2 1/2] linux-custom: add linux-tools package and build perf 'Isaac True' via isar-users
2025-11-27 7:22 ` 'Jan Kiszka' via isar-users [this message]
2025-11-26 13:02 ` [PATCH v2 2/2] doc: custom_kernel: add perf and linux-tools 'Isaac True' via isar-users
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=5a07dd76-3d55-4f02-841a-853f23b8c31c@siemens.com \
--to=isar-users@googlegroups.com \
--cc=itrue@emlix.com \
--cc=jan.kiszka@siemens.com \
/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