Re: The problem of packaging Minetest mods/games

[Jan <tona_kosmicznego_smiecia@interia.pl>]

Hi,

Thanks everyone for suggestions, I will check how it works in practice
and look for the environment variables.

Surprisingly I had an idea yesterday - what if we threat the minetest
package as an interpreter, which it actually is, because it interprets
lua scripts, while treating mods and games as files it
interprets. This way minetest doesn't require minetest-data as
a dependency anymore, on the other hand minetest-data requires minetest
to run, which is actually how it is in reality.

Following this idea, I removed the minetest-data dependency from the
minetest package and added minetest as a propagated input of
minetest-data. I installed the new minetest-data package and it worked!

This way minetest doesn't get rebuilt every time a modification/game is
added.

I could rename the packages:
minetest -> minetest-base/core (non-public package)
minetest-data -> minetest (public package)

This way installing minetest installs both the game's core and the
default game.

What do you think about this solution?



Jan Wielkiewicz