From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: buildroot@buildroot.org
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>
Subject: [Buildroot] [PATCH 0/1] utils/scanpypi: workaround for pypi project names
Date: Fri, 27 Mar 2026 08:43:53 +0200 [thread overview]
Message-ID: <20260327064354.5892-1-flaviu.nistor@gmail.com> (raw)
I want to purpose this patch and hope others find it useful.
While using scanpypi I noticed that for smmap2 package the modified .mk
.hash files where not correct, since smmap2 pypi project is just a
mirror of smmap and has different revision and hashes. I realized why the
problem exist only by reading the commit history of smmap2 and saw Thomas
Petazzoni's remark in commit: 8bc8f4c4161ddfd255615ce0962b570da20c4148.
The same is valid for gitdb2 package. To avoid this issue in the future
for this packages and others (as I'm sure there are similar cases),
I added a dictionary for buildroot packages that have a different
name compared to the pypi project name (e.g. smmap2 -> smmap).
Since there is no intention to change the buildroot package name,
this is a workaround in order to use the scanpypi utility for
this packages and still get correct generated files.
Other packages can be added in the dictionary as needed.
Flaviu Nistor (1):
utils/scanpypi: workaround for pypi project names
utils/scanpypi | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-27 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 6:43 Flaviu Nistor [this message]
2026-03-27 6:43 ` [Buildroot] [PATCH 1/1] utils/scanpypi: workaround for pypi project names Flaviu Nistor
2026-04-07 18:59 ` Arnout Vandecappelle via buildroot
2026-04-09 15:21 ` Flaviu Nistor
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=20260327064354.5892-1-flaviu.nistor@gmail.com \
--to=flaviu.nistor@gmail.com \
--cc=buildroot@buildroot.org \
/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