Date: Sat, 18 Dec 2021 12:10:53 -0700 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: Ed Maste <emaste@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: git: 30780c3f584a - stable/13 - README.md: correct GPL expansion Message-ID: <CANCZdfrOcxkfN1==7BjqYdwn8vUp5TbPpta8JaXkNez2TQHN%2Bw@mail.gmail.com> In-Reply-To: <4DFA25A9-4C30-4598-A694-4D818C5FAADA@yahoo.com> References: <B920DB5F-6D22-4C94-9C3D-CA35D8F8B212.ref@yahoo.com> <B920DB5F-6D22-4C94-9C3D-CA35D8F8B212@yahoo.com> <CAPyFy2BQc4JjF5Vq6X3=r4A1R5cVScgw5sLNWKoWc_7ZdthwoA@mail.gmail.com> <4DFA25A9-4C30-4598-A694-4D818C5FAADA@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Dec 18, 2021 at 11:33 AM Mark Millard via freebsd-current < freebsd-current@freebsd.org> wrote: > On 2021-Dec-18, at 09:30, Ed Maste <emaste@freebsd.org> wrote: > > > On Fri, 17 Dec 2021 at 11:09, Mark Millard <marklmi@yahoo.com> wrote: > >> > >> I'm confused, beyond just LGPL claims in the (fairly > >> current) source code, but GPL more generally: > >> > >> # grep -rl "SPDX.*GPL" /usr/main-src/ > > > > You need to exclude the ones with SPDX tags like: > > SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0 > > > > but also note that this text in README.md is just documenting the > > top-level gnu/ subdirectory. > > # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" > | grep -v sys/contrib/device-tree/ | more > /usr/main-src/sys/gnu/gcov/gcc_4_7.c:// SPDX-License-Identifier: GPL-2.0 > /usr/main-src/sys/gnu/gcov/gcov_fs.c:// SPDX-License-Identifier: GPL-2.0 > /usr/main-src/sys/dts/include/dt-bindings/soc/qcom,tcsr.h:/* > SPDX-License-Identifier: GPL-2.0 */ > > But . . . > > # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" > | grep sys/contrib/device-tree/ | wc > 3104 9958 345089 > Yea, that doesn't matter that much... Those are generally not used for tier 1 platforms, except for some arm64 boards. And when they are used, they create a separate work (the .dtb files). And that's even assuming these files are expressive enough to have enough creative content that a copyright could attach... It's not used at all the build kernels, userland, etc (though one does have an option to attach a dtb to a kernel, to be fair). And they are all well marked with SPDX tags, so we're not misrepresenting anything and the project's use of them is in full compliance with whichever GPL they are released under. Downstream users will, as with all license things, need to ensure their uses comply. There have been various statements about these files over the years which one should consult if one ships a system with the .dtb w/o the .dts sources to determine compliance measures necessary (though the standard GPL measures will work, some folks have disclaimed the need to do them for their .dts files, ymmv). Warner [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 18, 2021 at 11:33 AM Mark Millard via freebsd-current <<a href="mailto:freebsd-current@freebsd.org">freebsd-current@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2021-Dec-18, at 09:30, Ed Maste <<a href="mailto:emaste@freebsd.org" target="_blank">emaste@freebsd.org</a>> wrote:<br> <br> > On Fri, 17 Dec 2021 at 11:09, Mark Millard <<a href="mailto:marklmi@yahoo.com" target="_blank">marklmi@yahoo.com</a>> wrote:<br> >> <br> >> I'm confused, beyond just LGPL claims in the (fairly<br> >> current) source code, but GPL more generally:<br> >> <br> >> # grep -rl "SPDX.*GPL" /usr/main-src/<br> > <br> > You need to exclude the ones with SPDX tags like:<br> > SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0<br> > <br> > but also note that this text in README.md is just documenting the<br> > top-level gnu/ subdirectory.<br> <br> # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" | grep -v sys/contrib/device-tree/ | more<br> /usr/main-src/sys/gnu/gcov/gcc_4_7.c:// SPDX-License-Identifier: GPL-2.0<br> /usr/main-src/sys/gnu/gcov/gcov_fs.c:// SPDX-License-Identifier: GPL-2.0<br> /usr/main-src/sys/dts/include/dt-bindings/soc/qcom,tcsr.h:/* SPDX-License-Identifier: GPL-2.0 */<br> <br> But . . .<br> <br> # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" | grep sys/contrib/device-tree/ | wc<br> 3104 9958 345089<br></blockquote><div><br></div><div>Yea, that doesn't matter that much... Those are generally not used for tier 1 platforms, except</div><div>for some arm64 boards. And when they are used, they create a separate work (the .dtb files).</div><div>And that's even assuming these files are expressive enough to have enough creative content</div><div>that a copyright could attach... It's not used at all the build kernels, userland, etc (though one</div><div>does have an option to attach a dtb to a kernel, to be fair). And they are all well marked with</div><div>SPDX tags, so we're not misrepresenting anything and the project's use of them is in full</div><div>compliance with whichever GPL they are released under. Downstream users will, as with</div><div>all license things, need to ensure their uses comply. There have been various statements</div><div>about these files over the years which one should consult if one ships a system with the</div><div>.dtb w/o the .dts sources to determine compliance measures necessary (though the standard</div><div>GPL measures will work, some folks have disclaimed the need to do them for their</div><div>.dts files, ymmv).</div><div><br></div><div>Warner</div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrOcxkfN1==7BjqYdwn8vUp5TbPpta8JaXkNez2TQHN%2Bw>