Relicensing MT under LGPLv2.1

[LRV]

The LGPLv2.1 prevents from including functions, which require input other than when invoked. However, plenty of functions call other functions to reuse their return value, meaning they need input after invokation. Does that mean MT may only be relicensed under GPLv3?

[LibraSubtilis]

An interesting question. Can you specify the parts of the license you talk about?

[rubenwardy]

Not a lawyer, but LGPLv2.1 can only be relicensed to GPLv2.1 or AGPLv2.1. You can still write your own mods in whatever license you want because it doesn't count as linking

[Wuzzy]

OK, let's be pragmatic here:
Is there any ACTUAL and CONCRETE problem the current license is causing RIGHT NOW? Do you have any SPECIFIC use case? If yes, then we can look into that in detail and try to find a solution.

If no, I don't think this discussion isn't very helpful.

[LRV]

First of all, MT Engine and most game mods are licensed under LGPLv2.1+, meaning you can relicense it as GPLv2, GPLv3, LGPLv2.1, LGPLv3 directly, and through the relicensing options of GPLv3 as AGPLv3.

My specific use case would be a mod that modifies minetest.get_node_dig to pass certain values to a custom minetest.get_node_drops. For that I'd need add sth like "digger:get_wielded_item()". This calls the function get_wielded_item, but outside when my custom minetest.get_node_drops is first invoked, which violates LGPLv2.1 and LGPLv3 terms, forcing me to revert to one of the other licenses.