> The problem with this is that you can't really achieve this.
> have the minetest enabled by default. Plus, this would mean that you
> couldn't run a minetest server without installing the full game. IMHO,
> it's best to keep them separate.
Let me describe it in details.
There are two packages: minetest-server and minetest.
1) minetest-server package can be installed on the server without
Xorg. It does not depend on the package minetest. It provides
minetestserver binary and it can be run system-wide using the command
systemctl minetest.service start
It starts the simple daemon, which is listening the port 30000, and it
uses /var/lib/minetest to store server data.
2) minetest is the package containg the client. It provides the
minetest binary. And it depends on the package minetest-server.
When you run minetest as user, there are two possibilities:
- If you put anything in the "Server" field (this might be localhost
also), then minetest tries to connects to the server which is already
- If you leave this field blank, then it runs its own separate
minetestserver process in the user-space, with user privileges only.
And it saves all the server data in user home directory.
Thus i need this dependency (minetest depending on the
minetest-server) to provide this second possibility to run the simple
single player instance without need to start the system-wide service.
So right now from the user-side it works easy like this:
$ yum install minetest
set the Username , leave Server field blank and push the Run button.
I see. So I understand the need for the minetest package to require the
minetest-server package. But the possibility that someone might want to
run a minetest server on a non-client machine would be a good reason to
keep them separate.
bookwar at freenode
in your fear, seek only peace
in your fear, seek only love