From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 3/5] toolchain-external-linaro*: Add support for license file description
Date: Wed, 28 May 2025 18:46:17 +0200 [thread overview]
Message-ID: <20250528184617.1f4b9130@windsurf> (raw)
In-Reply-To: <20250528-fix_license_toolchain-v1-3-34295630709b@bootlin.com>
On Wed, 28 May 2025 16:58:00 +0200
Kory Maincent <kory.maincent@bootlin.com> wrote:
> +sha256 c069e5dfe15e372d25b17c4124a5f8dd55b9f191d633f5954cdb766f8f23eaa9 share/info/annotate.info
> +sha256 2551fc28dc6c6b756f9612b3f89c4fb485c9694fc5966aa214d7f408bce80519 share/info/as.info
> +sha256 0c1abdf8a8f14779464095c0713012d84c7f953a07cb95e3bc96a82a9cdbf53d share/info/bfd.info
> +sha256 e941845f6e6b949fe7108fb37e12d69618c194242ee3b4a017a9f83de9dd6413 share/info/binutils.info
> +sha256 c391849998371cfcb37f9b2be89a05741c575a4393334b7592496aa560074b1b share/info/cpp.info
> +sha256 37275dbe06c98068171b22a0ae42ef081e2e9ad46b362f858cd20b92681ea208 share/info/cppinternals.info
> +sha256 c17fe3000a0567e1d8222b3ea84c0486a6ddce560751ca52a8114f9da698cacf share/info/gcc.info
> +sha256 0bdd496d8869610781ce7597d416b5e0766201a400e8e07189303d385a9f57a7 share/info/gccinstall.info
> +sha256 25b3fa627982d60491253dc54babb1181ea48d428a433fc4a6526ec20831f5d4 share/info/gccint.info
> +sha256 1aa3708b21aef829201ddc1905269ae4e9878a55519c71bc1cb95e5a4acdfcff share/info/gdb.info
> +sha256 b4d8ce068704b9ea8f3a53e2854665dc79faa368ccfc2378e02145a8600372f8 share/info/gfortran.info
> +sha256 bc690ceaef812eb24ff78db7c126c7c437e4ac28735b574f0a26156bfa1d1814 share/info/gmp.info
> +sha256 2c6c34554dc0510af68276ec25ac40aec8c60adb9d342754a4ecf91af31c3d96 share/info/gmp.info-1
> +sha256 68920853733f61b4c7bfd1136a7590da2dd6d131f2c2e87e271cd32415b477e3 share/info/gmp.info-2
> +sha256 4d9f0af46c653b9a5a67c472b08cf25723ff717c138691ac6616e583544aba84 share/info/gprof.info
> +sha256 b84087feb8b8fae12f74a66aa047b662c7b792cee730cc82fd3a614fe613b6af share/info/ld.info
> +sha256 e55fcf49ee60c48fa5890df1c39fb49660c24c56768c7025f531e02513eb64d2 share/info/libgomp.info
> +sha256 6217bcbd1f2e626ad11ec95b660eb3ee46ed643e17eb91c191c075ca4bf753cd share/info/libitm.info
> +sha256 231a4ff2f3dc0f01091f3ca0720dbcf1374441a5c9fc82a4903d8b07e85dd8fa share/info/mpc.info
> +sha256 9d125638fe0cb17b98434af9ed52630fd443653d87a88d1e5be42c92abca355f share/info/mpfr.info
> +sha256 83a110dcc363139c652eef0a6d8061e91df3d0e56e3cb46b172ea6c61638364e share/info/stabs.info
I guess those info files are the full documentation of gdb, gcc, as,
etc. ? They will change very often, completely unrelated to the license
changes, no?
> +TOOLCHAIN_EXTERNAL_LINARO_AARCH64_BE_LICENSE = multiple
I'm wondering if stating "multiple" really helps. Shouldn't we actually
list the licenses?
The concern I have is that a toolchain-external package is really just
a target package, so we can't distinguish easily what goes on the
target vs. what stays on the host and that's quite important
license-wise. This is BTW why we introduced the gcc-runtime package
when Buildroot is building the toolchain, it allows to clarify the
licensing of host packages (host-gcc, host-binutils, host-gdb) vs. the
licensing of what goes into the target (gcc-runtime).
Should we make external toolchain packages host packages, and have a
single target package like toolchain-external-runtime that takes care
of copying things over to staging/target ? (But then if the licensing
is different per toolchain that's annoying). Or should each external
toolchain package be both a target and a host package ?
Many questions for which I don't have immediate answers I must admit.
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:[~2025-05-28 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 14:57 [Buildroot] [PATCH 0/5] Add support for license files for external toolchain Kory Maincent via buildroot
2025-05-28 14:57 ` [Buildroot] [PATCH 1/5] toolchain-external: Fix license file management after toolchain move Kory Maincent via buildroot
2025-05-28 16:40 ` Thomas Petazzoni via buildroot
2025-06-02 15:02 ` Kory Maincent via buildroot
2025-05-28 14:57 ` [Buildroot] [PATCH 2/5] toolchain-external-bootlin: Add support for license file description Kory Maincent via buildroot
2025-05-28 14:58 ` [Buildroot] [PATCH 3/5] toolchain-external-linaro*: " Kory Maincent via buildroot
2025-05-28 16:46 ` Thomas Petazzoni via buildroot [this message]
2025-06-02 14:49 ` Kory Maincent via buildroot
2025-10-06 13:18 ` Kory Maincent via buildroot
2025-05-28 14:58 ` [Buildroot] [PATCH 4/5] toolchain-external-arm*: " Kory Maincent via buildroot
2025-05-28 14:58 ` [Buildroot] [PATCH 5/5] toolchain-external-codesourcery-mips: " Kory Maincent via buildroot
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=20250528184617.1f4b9130@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=kory.maincent@bootlin.com \
--cc=romain.naour@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