From: "'Florian Bezdeka' via isar-users" <isar-users@googlegroups.com>
To: Isaac True <itrue@emlix.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] linux-custom: add linux-tools package and perf
Date: Wed, 26 Nov 2025 11:30:27 +0100 [thread overview]
Message-ID: <0051ff6123997ce7e47738e3a1dc004b46f7ee16.camel@siemens.com> (raw)
In-Reply-To: <ba94b97e-cb49-4b73-93d3-8be1e00991b2@emlix.com>
On Wed, 2025-11-26 at 10:59 +0100, Isaac True wrote:
> Hi,
>
> > Patch ordering:
> > Patch 1 already adds the new package to PROVIDES while building the
> > package comes later with patch 2. That looks inconsistent.
> >
> > I would vote for merging patch 1 and 2.
>
> Sure, that makes sense. I can do that.
>
> > How long does it take to build that additional package? That additional
> > (and maybe unneeded) packet is being build unconditionally, right? As
> > kernel builds are normally compute intense that might matter for some
> > users.
> >
> > Should we better hide that new "feature" / packet behind a feature flag
> > / recipe variable?
>
> On my relatively slow laptop it adds about 30s of build time. Relatively
> minor in the context of a kernel build, but could still be worth hiding
> it behind a feature flag for people that don't want it.
The way to model that would be a build profile (DEB_BUILD_PROFILES) as
it seems. I'm still not sure if that is really necessary. As that could
be done quite easily (as it seems) we can also postpone that and wait if
it becomes necessary.
>
> Thanks for the feedback, I'll work on a v2.
>
> --
> Isaac True
> emlix GmbH
> Headquarters: Berliner Str. 12, 37073 Göttingen, Germany
> Phone +49 (0)551 30664-0, e-mail info@emlix.com
> District Court of Göttingen, Registry Number HR B 3160
> Managing Directors: Heike Jordan, Dr. Uwe Kracke
> VAT ID No. DE 205 198 055
> Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
> Office Bonn: Bachstr. 6, 53115 Bonn, Germany
> Office München: Am Knie 16, 81241 München, Germany
> http://www.emlix.com
>
> emlix - your embedded Linux partner
--
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/0051ff6123997ce7e47738e3a1dc004b46f7ee16.camel%40siemens.com.
next prev parent reply other threads:[~2025-11-26 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 8:59 'Isaac True' via isar-users
2025-11-26 8:59 ` [PATCH 1/3] linux-custom: add linux-tools package 'Isaac True' via isar-users
2025-11-26 8:59 ` [PATCH 2/3] linux-custom: build perf and add it to linux-tools 'Isaac True' via isar-users
2025-11-26 9:09 ` 'Isaac True' via isar-users
2025-11-26 8:59 ` [PATCH 3/3] doc: custom_kernel: add perf and linux-tools 'Isaac True' via isar-users
2025-11-26 9:46 ` [PATCH 0/3] linux-custom: add linux-tools package and perf 'Florian Bezdeka' via isar-users
2025-11-26 9:59 ` 'Isaac True' via isar-users
2025-11-26 10:30 ` 'Florian Bezdeka' via isar-users [this message]
2025-11-27 7:17 ` 'Jan Kiszka' 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=0051ff6123997ce7e47738e3a1dc004b46f7ee16.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=florian.bezdeka@siemens.com \
--cc=itrue@emlix.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