From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists--- via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/python-pylibfdt: new package
Date: Sat, 23 Jul 2022 21:20:26 +0200 [thread overview]
Message-ID: <20220723212026.6cf8d13c@windsurf> (raw)
In-Reply-To: <20220511080148.5084-1-yegorslists@googlemail.com>
On Wed, 11 May 2022 10:01:48 +0200
yegorslists--- via buildroot <buildroot@buildroot.org> wrote:
> +PYTHON_PYLIBFDT_VERSION = 1.6.1
> +PYTHON_PYLIBFDT_SOURCE = pylibfdt-$(PYTHON_PYLIBFDT_VERSION).tar.gz
> +PYTHON_PYLIBFDT_SITE = https://files.pythonhosted.org/packages/15/3c/40b1d6a1df9dbc9d9ba5700a47ad95ca1e984f18daf25ede0da5f67d0cf7
> +PYTHON_PYLIBFDT_SETUP_TYPE = setuptools
> +PYTHON_PYLIBFDT_LICENSE = BSD-2-Clause, GPL-2.0+
According to the SPDX tags in the code, the license is BSD-2-Clause
*OR* GPL-2.0+, so I changed that here, and applied.
I hope this will not cause any conflict with the bundled pylibfdt that
exists in U-Boot for example, but we'll see :-)
A short comment on those new Python packages: it would sometimes be
useful to have a corresponding runtime test in the support/testing/
infra, as it helps ensure that the dependencies have been properly
taken into account in the packaging.
Thanks!
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
prev parent reply other threads:[~2022-07-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 8:01 [Buildroot] [PATCH] package/python-pylibfdt: new package yegorslists--- via buildroot
2022-07-23 19:20 ` Thomas Petazzoni via buildroot [this message]
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=20220723212026.6cf8d13c@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@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