From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/3] package/python-poetry-core: new host package
Date: Tue, 6 Feb 2024 21:47:35 +0100 [thread overview]
Message-ID: <20240206214735.7d69db1e@windsurf> (raw)
In-Reply-To: <20240206193048.658003-1-james.hilliard1@gmail.com>
On Tue, 6 Feb 2024 12:30:46 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> +PYTHON_POETRY_CORE_LICENSE = \
> + Apache-2.0 or BSD-2-Clause (packaging), \
> + BSD-3-Clause (fastjsonschema), \
> + GPL-2.0-or-later (lark), \
Didn't review the licensing, but in Buildroot we diverge from SPDX on
this point, and we encode GPL-2.0-or-later as GPL-2.0+.
No need to resend just for that, it can be fixed when applying.
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
next prev parent reply other threads:[~2024-02-06 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 19:30 [Buildroot] [PATCH v3 1/3] package/python-poetry-core: new host package James Hilliard
2024-02-06 19:30 ` [Buildroot] [PATCH v3 2/3] package/python-pypika-tortoise: new package James Hilliard
2024-02-06 19:30 ` [Buildroot] [PATCH v3 3/3] package/python-tortoise-orm: " James Hilliard
2024-02-06 20:47 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-30 15:25 [Buildroot] [PATCH v3 1/3] package/python-poetry-core: new host package James Hilliard
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=20240206214735.7d69db1e@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@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