From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas Perale <thomas.perale@mind.be>,
Christian Stewart <christian@aperture.us>,
Arnout Vandecappelle <arnout@rnout.be>
Subject: [Buildroot] [PATCH 6/7] package/pkg-python: support PURL generation
Date: Tue, 15 Apr 2025 21:55:40 +0200 [thread overview]
Message-ID: <20250415195547.199428-8-thomas.perale@mind.be> (raw)
In-Reply-To: <20250415195547.199428-1-thomas.perale@mind.be>
The PURL specification for python packages follows the coordinates from
the sonatype ossindex:
https://ossindex.sonatype.org/ecosystem/pypi
- The PURL type is 'pypi'.
- The PURL name is the package name. Since buildroot python packages
include a 'python-' prefix to the name of package, this part is
stripped.
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
package/pkg-python.mk | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/package/pkg-python.mk b/package/pkg-python.mk
index 32ace4aac1..c125b2e009 100644
--- a/package/pkg-python.mk
+++ b/package/pkg-python.mk
@@ -454,6 +454,22 @@ endif
endif # host / target
+ifndef $(2)_PURL_TYPE
+ ifdef $(3)_PURL_TYPE
+ $(2)_PURL_TYPE = $$($(3)_PURL_TYPE)
+ else
+ $(2)_PURL_TYPE = pypi
+ endif
+endif
+
+ifndef $(2)_PURL_NAME
+ ifdef $(3)_PURL_NAME
+ $(2)_PURL_NAME = $$($(3)_PURL_NAME)
+ else
+ $(2)_PURL_NAME=$$(patsubst python-%,%,$$($(2)_RAWNAME))
+ endif
+endif
+
# Call the generic package infrastructure to generate the necessary
# make targets
$(call inner-generic-package,$(1),$(2),$(3),$(4))
--
2.49.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-15 19:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 19:55 [Buildroot] [PATCH 0/7] Add PURL support Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 1/7] package/pkg-generic.mk: add PURL package variable Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 2/7] package/pkg-download: add 'owner' macro Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 2/7] package/pkg-download: add repository macro Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 3/7] package/pkg-golang: support PURL generation Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 4/7] package/pkg-cargo: " Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 5/7] package/pkg-perl: " Thomas Perale via buildroot
2025-04-15 19:55 ` Thomas Perale via buildroot [this message]
2025-04-15 19:55 ` [Buildroot] [PATCH 7/7] package/pkg-utils: add PURL to show-info output Thomas Perale via buildroot
2025-04-16 19:07 ` [Buildroot] [PATCH 0/7] Add PURL support Peter Korsgaard
2025-04-16 19:19 ` Arnout Vandecappelle via buildroot
[not found] ` <4b029329-2258-428d-80c9-315dbd6335be@essensium.com>
2025-04-16 19:58 ` Thomas Petazzoni via buildroot
2025-04-16 20:06 ` Thomas Perale via buildroot
2025-04-16 20:40 ` Thomas Petazzoni via buildroot
2025-04-16 20:49 ` Thomas Perale via buildroot
2025-04-18 10:39 ` Thomas Petazzoni via buildroot
2025-04-21 20:19 ` Thomas Perale via buildroot
2025-04-22 12:53 ` Thomas Petazzoni via buildroot
2025-04-22 14:00 ` 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=20250415195547.199428-8-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=christian@aperture.us \
--cc=thomas.perale@mind.be \
--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