From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Michael Klein via buildroot <buildroot@buildroot.org>
Cc: Michael Klein <m.klein@mvz-labor-lb.de>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 1/1] size-stats: count compiled python (.pyc) files
Date: Sat, 24 Sep 2022 10:35:46 +0200 [thread overview]
Message-ID: <20220924103546.00681d4f@windsurf> (raw)
In-Reply-To: <YxCaF6FKRqXSPeWS@LLGMVZLB-0037>
On Thu, 1 Sep 2022 13:40:07 +0200
Michael Klein via buildroot <buildroot@buildroot.org> wrote:
> Any .pyc files generated by the pycompile script during target
> finalization are currently counted in the "Unknown" package,
> because packages-file-list.txt only contains the source .py file.
>
> If a .py file is added to filesdict, add the corresponding .pyc
> file as well.
>
> Signed-off-by: Michael Klein <m.klein@mvz-labor-lb.de>
> ---
> support/scripts/size-stats | 3 +++
> 1 file changed, 3 insertions(+)
We indeed don't have a very good mechanism to "connect" files generated
during the target-finalize step with their original package in a
generic way, so for now what you did is I believe good enough to solve
this very common case of .pyc files, and therefore I've applied to
master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-24 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 11:40 [Buildroot] [PATCH 1/1] size-stats: count compiled python (.pyc) files Michael Klein via buildroot
2022-09-24 8:35 ` Thomas Petazzoni [this message]
2022-09-30 15:11 ` Peter Korsgaard
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=20220924103546.00681d4f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=m.klein@mvz-labor-lb.de \
--cc=thomas.de_schampheleire@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.