The basic idea would be to clone the version of the game I'm playing in a working directory, do some changes (custom species mainly), and then update my own game (/usr/share/games/freeorion). I'm still not sure how to do that last part.
This part I don't understand. How would git know that if I just copy (I guess you mean manually, e.g. with cp) files to a directory that's not part of a git project?Dilvish wrote: ↑Sun May 20, 2018 5:07 pmSince you are thinking about contributing to the project, I'd highly recommend you read up a little bit on using Git. That tool (via github) is the way such contributions get submitted, and using it would also automatically track your modified files.Jaumito wrote:I just need to remember which ones I had to alter - stringtables, the pedia, the common macros stuff, etc. - I think there's about a dozen of them.
I am pretty sure if you make a local git repo, and then make a branch checking out the exact same commit as corrsponds to the version of FO you are playing now (either the version number tag or a sufficient portion of the relevant commit will be embedded into the version name displayed ingame), then you could just copy your entire modified 'default' directory over the one in your local git repo, and git would automatically figure out which files had been modified (and what those modifications were).
What I'd like would be to make git aware I'm supposed to commit (and undo) changes to my local version of the game. Isn't there a way to do that? Or should I just build a second freeorion from my local repo?