All of lore.kernel.org
 help / color / mirror / Atom feed
From: <yann.morin@orange.com>
To: <buildroot@buildroot.org>
Cc: Vincent Fazio <vfazio@xes-inc.com>,
	"Yann E . MORIN" <yann.morin@orange.com>
Subject: [Buildroot] [PATCH 0/2 v2] support/size-stats: actually handle .pyc files
Date: Mon, 14 Sep 2026 14:48:43 +0200	[thread overview]
Message-ID: <cover.1789390115.git.yann.morin@orange.com> (raw)

From: "Yann E. MORIN" <yann.morin@orange.com>

Hello All!

This small two-patch series properly associates .pyc files to the
corresponding package, to account for the PEP 3147 layout.

Changes v1 -> v2:
  - use python's cache_from_source() instead of open-coding the
   path  (Vincent)


Regards,
Yann E. MORIN.


The following changes since commit 04d7d7bdeb907483e7db0005b403484f379cf84b

  package/mosh: bump gcc version requirement due to protobuf (2026-09-13 21:59:28 +0200)


are available as patches in this mail series,

for you to apply patches up to 9e49dfb4368becd006de1be4977695caea90c237

  support/scripts/size-stats: properly assign pre-compiled .pyc files (2026-09-14 14:29:42 +0200)


----------------------------------------------------------------
Yann E. MORIN (2):
      support/scripts/size-stats: prepare for more .py associated files
      support/scripts/size-stats: properly assign pre-compiled .pyc files

 support/scripts/size-stats | 31 ++++++++++++++++++++++++++++---
 1 file changed, 28 insertions(+), 3 deletions(-)

--
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-09-14 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 12:48 yann.morin [this message]
2026-09-14 12:48 ` [Buildroot] [PATCH 1/2 v2] support/scripts/size-stats: prepare for more .py associated files yann.morin
2026-09-14 12:48 ` [Buildroot] [PATCH 2/2 v2] support/scripts/size-stats: properly assign pre-compiled .pyc files yann.morin
2026-09-17  8:57 ` [Buildroot] [PATCH 0/2 v2] support/size-stats: actually handle " yann.morin
2026-09-17 20:29   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2026-09-18  4:45 yann.morin
2026-09-21 12:42 ` Vincent Fazio
2026-10-08 17:21 ` yann.morin

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=cover.1789390115.git.yann.morin@orange.com \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.org \
    --cc=vfazio@xes-inc.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.