Re: Combined version of LGPL + GPL 3.0
~ J Lovejoy [2021-07-28 17:34 +0200]:
On 7/28/21 9:08 AM, Max Mehl wrote:From my understanding, they did not want to treat LGPL-3.0 as anDo I understand correctly that FSF still doesn't think of LGPL-3.0 as anto clarify: the FSF turned down GPL-3.0* WITH LGPL-3.0* orexception to GPL-3.0 (even though functionally and structurally it is)Yes, that was a suggestion made by Matija in the discussion we've had.
exception to GPL-3.0. So they turned down "GPL-3.0* WITH LGPL-3.0*".
"GPL-3.0 AND LGPL-3.0" as well as "GPL-3.0 OR LGPL-3.0" is no problem in
the REUSE space. You'd have both license texts in LICENSES/ which is
what is missing if you just mark files as LGPL-3.0.
That's interesting. If this was the case, the whole problem would notNow, we have a concatenated version. The license effectively did notFrom a practical perspective: the LGPL-3.0 clearly states at the top,
exist. However, in the issue I've shared this was identified as a
problem by multiple persons.
I have seen, in practice, people include the text of both in the COPYINGAck that this method could create confusion. However, with the
combination of a concatenated version under "LICENSES/LGPL-3.0-only.txt"
and "SPDX-License-Identifier: LGPL-3.0-only" in the file header, I
cannot see any practical confusion.
Sure, the full GPL text is present in the LGPL...txt file, but given its
file name and the SPDX tag, it should be obvious what's meant.
Our understanding was that SPDX was unhappy with the current situationI am afraid that compliance issues have been caused *before* this changeBy compliance issues, do you mean compliance with the REUSE spec?
but did not succeed in making the FSF change their treatment of LGPL in
either direction (exception or concatenation). That is why we went the
short informal route.
I acknowledge that this was not perfect given the backlash that comes up
In any case, I think it's good to have the discussion with allSure, that's also why I propose it here ;)
My availability in August will be close to zero though, but perhaps
Matija can chime in who was present in the call and a leading force
behind this anyway :)
Max Mehl - Programme Manager - Free Software Foundation Europe
Contact and information: https://fsfe.org/about/mehl | @mxmehl
Become a supporter of software freedom: https://fsfe.org/join