From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies
Date: Mon, 11 Aug 2025 22:28:27 +0200 [thread overview]
Message-ID: <20250811222827.4a74af55@windsurf> (raw)
In-Reply-To: <d483d5ac-58f7-4517-b049-3a7688b83d2f@gmx.de>
Hello,
On Mon, 11 Aug 2025 12:53:52 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:
> Something like "record a trace and process it into
> statistics/flamegraph" should be simple enough to do, checking if the
> output makes sense would be hard to automate though. Would just "doesn't
> crash in the process" and maybe a grep for expected items be enough?
Something simple is good enough. Verifying that the output "makes
sense" is IMO too complicated. Just make sure that it does generate
something vaguely reasonable :-)
> I'll add it then. Would it make sense to use "depends on" the new option
> in package/python-memray then, to simplify the forwarded requirements
> (instead of copying all the "depends on" for elfutils and json-c), even
> if it's a little less convenient to enable?
I saw you v2, and you went for "select", and it was the right thing to
do. Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-11 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 22:32 [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 1/7] package/elfutils: enable libdebuginfod for target if requirements are met Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 2/7] package/python-mdurl: new package Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 3/7] package/python-markdown-it-py: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 4/7] package/python-platformdirs: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 5/7] package/python-rich: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 6/7] package/python-textual: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 7/7] package/python-memray: " Fiona Klute via buildroot
2025-08-10 10:47 ` [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies Thomas Petazzoni via buildroot
2025-08-11 10:53 ` Fiona Klute via buildroot
2025-08-11 20:28 ` Thomas Petazzoni via buildroot [this message]
2025-08-11 20:52 ` Thomas Petazzoni via buildroot
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=20250811222827.4a74af55@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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