bits 0x50 - Calender Week 16, 2024

> Public Licenses
GPL has been quite some headache for me recently: not in the way that I have problem with its progressive ideology, but the compatibility terms.

First, the GPL licenses are not necessarily compatible within the GPL family:
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility

Take GPLv2 and GPLv3 or example, I want to incorporate two code components, A and B into my project (components as code, not libraries).

                        | License of Component A
                        |---------+-----------------------------+
                        | GPLv2 o | GPLv2 + | GPLv3 o | GPLv3 + |
------------+-----------+---------+---------+---------+---------+
License     | GPLv2 o   | Yes     |
of          |-----------+---------+---------+
Component   | GPLv2 +   | Yes     | Yes     |
B           |-----------+---------+---------+---------+
            | GPLv3 o   | No      | Yes     | Yes     |
            |-----------+---------+---------+---------+---------+
            | GPLv3 +   | No      | Yes     | Yes     | Yes     |
------------+-----------+---------+---------+---------+---------+

o means only
+ means or-later
X imcompatible: there is no license that is compatible with both A and B

GPLv2-only (such as the linux kernel) and GPLv3-only/-or-later are not compatible.

Take another example: GPL also applies to library: if you write a kernel module, which is (and must be) linked against the linux kernel code, it has to be compatible with GPLv2-only (if you want a copyleft license).

GPLv3 is not compatible with GPLv2, sorry, you can not have GPLv3-only kernel modules, it’s impossible. https://github.com/jarun/spy/issues/1#issuecomment-147501332

GPL is hardly compatible with other copyleft licenses
I recently learned about the EUPL . It looks really appealing but then I see the issue:

https://joinup.ec.europa.eu/collection/eupl/matrix-eupl-compatible-open-source-licences

You can incorporate EUPL licensed code into GPL project but not vice versa! Well, GPL is immutable, that’s the point of GPL no?

Nevertheless, I’d like to try EUPL in the future.

Good Reads

Why X86 needs to die - by Julian Scheffers
https://hackaday.com/2024/03/21/why-x86-needs-to-die/

Learns

Fun

MISC

[+] click to leave a comment [+]
the comment system on this blog works via email. The button
below will generate a mailto: link based on this page's url 
and invoke your email client - please edit the comment there!

[optional] even better, encrypt the email with my public key

- don't modify the subject field
- specify a nickname, otherwise your comment will be shown as   
  anonymous
- your email address will not be disclosed
- you agree that the comment is to be made public.
- to take down a comment, send the request via email.

        
>> SEND COMMENT <<
[BITS] - the weekly archive -
bits 0x51 - Calender Week 16, 2024 (WIP)
bits 0x50 - Calender Week 16, 2024
bits 0x49 - Calender Week 15, 2024
bits 0x48 - Calender Week 14, 2024
bits 0x47 - Calender Week 13, 2024
bits 0x46 - Calender Week 12, 2024
bits 0x45 - Calender Week 11, 2024
bits 0x44 - Calender Week 10, 2024
bits 0x43 - Calender Week 09, 2024 [VOID]
bits 0x42 - Calender Week 08, 2024 [VA]
bits 0x41 - Calender Week 07, 2024 [VOID]
bits 0x40 - Calender Week 06, 2024 [VOID]
bits 0x39 - Calender Week 05, 2024
bits 0x38 - Calender Week 04, 2024
bits 0x37 - Calender Week 03, 2024
bits 0x36 - Calender Week 02, 2024 [VA]
bits 0x35 - Calender Week 01, 2024
bits 0x34 - Calender Week 52, 2023
bits 0x33 - Calender Week 51, 2023
bits 0x32 - Calender Week 50, 2023 [VOID]
bits 0x31 - Calender Week 49, 2023
bits 0x30 - Calender Week 48, 2023
bits 0x2f - Calender Week 47, 2023
bits 0x2e - Calender Week 46, 2023
bits 0x2d - Calender Week 45, 2023
bits 0x2c - Calender Week 44, 2023
bits 0x2b - Calender Week 43, 2023
bits 0x2a - Calender Week 42, 2023