William Breathitt Gray

We encountered this issue in Gentoo. Using the HOME env variable can work if the user wants to use that location, but some users prefer to store their game data...

> How about `HOME=/path/to/data minetestserver ...etc` ? Does that not work, or not have the expected results? This assumes the user is running a shell such as bash that can...

As long as the environment variable is named something sufficiently unique (e.g. `MINETEST_USERDATA` or similar) then I think that approach should be okay because we avoid the clobbering `HOME` issue.

@Zughy No one's contacted me with any updates, so I don't know what the state of this is. I think the only change needed is a single line in the...

I apologize, I was under the impression someone else had already started working on this. It's no problem, I will code something up later today for this and submit it....

I'm closing this PR in favor of https://github.com/minetest/minetest/pull/12639.

@tpoindex Would you update this pull request to make the change you suggested to set `progressive=not args.defer_output`?

I updated the Fdroid `au.id.micolous.farebot` metadata to autoupdate the Fdroid package whenever a new Metrodroid release is tagged. However, we discovered a minor issue in the Metrodroid *build.gradle* file: [the...

Since **versionCode** is just a git rev-list count from HEAD, it can be reimplemented as a [pre-commit git hook](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks). Just put the following bash script in `.git/hooks/pre-commit`: ```bash #!/bin/sh versionCode=$(($(git...

After giving it some more thought, I think the best setup is to hardcode both the **versionCode** and **versionName** lines, updating with each tagged release. My rationale is that the...