bindings: python: do we need to distribute the LICENSE? #162
Description
As I regularly contribute to Buildroot, I monitor their mailing list for submissions.
This came in yesterday: https://lists.buildroot.org/pipermail/buildroot/2025-November/790133.html
Buildroot has a make target that aggregates all of the license files for software included in a build. I think this is for compliance purposes.
Right now, the bindings refer to LGPL 2.1 in pyproject.toml but we do not include a copy of the license as part of the distribution.
As such, when building this license bundle, they have to resort to copying in pyproject.toml since it's what calls out the effective license for the package.
I'm not familiar with license shenanigans, but this may be covered as part of PEP 639 where we could include a copy of the effective license into the python bindings subtree and reference it like so:
[project]
license-files = ["LICENSE"]Whether it should be LICENSE or COPYING or COPYING.LESSER, I don't know. GNU has their thoughts on it but I don't know if that is convention or has to be strictly adhered to.