[patemmschmitz]

For me - correct me if I'm wrong, the tivoization issue looks mostly related to what is really a "derivative" of your work (i. e. in case the level of dependency of some hardware device that uses/incoprporate your software is so high that it can be considered as a derivative). For this reason the EUPL-1.2 covers "the Work", that could be software code, ancillary data, documentation, or even hardware in so far it could be considered as a derivative.

[palata]

Hmm not sure. Tivoization is about distributing a product together with the source code running on it, but without giving a mean to update the software.

That's the difference between GPLv2 and GPLv3: if you buy an Android smartphone, you are entitled to receive the Linux source code for that smartphone. But maybe there is a secure boot and it is impossible for you to flash an updated version of Linux.

GPLv3 says that not only you should receive the source code, but also instructions about how to flash your own version of the covered software.

It feels like EUPL is closer to GPLv2 in that sense, right? Which is fine, but it's good to know.