Re: [PATCH 08/18] libtasn1: import libtasn1-4.16.0

[Daniel Axtens]

Hi Konrad,

>> +LICENSING
>> +=========
>> +
>> +The libtasn1 library is released under the GNU Lesser General Public
>> +License (LGPL) version 2.1 or later; see 
>> [COPYING.LESSER](doc/COPYING.LESSER)
>> +for the license terms.
>> +
>> +The GNU LGPL applies to the main libtasn1 library, while the
>> +included applications library are under the GNU GPL version 3.
>> +The libtasn1 library is located in the lib directory, while the applications
>> +in src/.
>
> GRUB is GPL-v3. This is not.
>
> Can you re-license it to be GPL-v3?

I believe we can combine and ship these together: any distribution of
grub that is compliant with GPLv3+ will also be compliant with
LGPLv2.1+. I source this from:

https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility

Or are you suggesting that we should additionally re-license the files
we import from LGPL to GPL per section 3 of LGPL2.1?

|   3. You may opt to apply the terms of the ordinary GNU General Public
| License instead of this License to a given copy of the Library.  To do
| this, you must alter all the notices that refer to this License, so
| that they refer to the ordinary GNU General Public License, version 2,
| instead of to this License.  (If a newer version than version 2 of the
| ordinary GNU General Public License has appeared, then you can specify
| that version instead if you wish.)  Do not make any other change in
| these notices.

I don't have strong feelings either way.

We already include MIT-licensed "jsmn" code our GPLv3 json module, so it
wouldn't be a change from our usual practice to include GPLv3-compatible
code by wrapping it in a module that claims GPLv3.

Kind regards,
Daniel