temporary problems when pulling and updating

[andy5995]

To make things easier for contributors, I removed the submodule method.

What this means is that if you've already cloned the repo using git clone --recursive... you are likely to have problems the next time you use mk/linux/git_update.sh

Everything should be set right now, but I'm sorry to say that it will be easier for most people to re-clone the source and data repo into a different different directory.

The new instructions have been documented

https://github.com/ZetaGlest/zetaglest-source#try-the-game-without-contributing

People who have cloned forks for the purpose of contributing may have an easier time, but I've also updated those instructions as well:

https://github.com/ZetaGlest/zetaglest-source/blob/develop/CONTRIBUTING.md#set-up-the-repositories-locally

My apologies for the inconvenience.

[andy5995]

Another change... @Jammyjamjamman and I thought separating the source and data repos would be a good idea.

Links to changes are shown in zetaglest/zetaglest-source@534d2ae

If you've cloned the repos within the last week, the only thing you should need to do, from zetaglest-source/ is

mv data ../zetaglest-data (be sure no zetaglest-data/ dir already exists or data will be moved into zetaglest-data/)

To verify zetaglest can find the new location, just run zetaglest from its usual location.

If you run into problems, just give us a holler

[andy5995]

This was only a short-term issue.