This might be my own "user error", something overlooked in the ebuild, or an upstream bug. Before this version, in a local game (where the server isn't started manually), games used to be saved automatically to "~/.freeciv/saves/", but they are apparently now going by default to the user's home directory ("~/"). This rapidly clutters the root of the user's home directory (especially since the game is, by default, saved at the end of every turn now, with a different name, populating the directory with literally hundreds of files). Moreover, while this *can* be controlled easily when starting the server *manually*, by setting the "[ -s|--saves directory ]" option, there doesn't seem to be any other way to select the save location. There is no setting the server can change at runtime, so it can't be defined in a server startup script. It cannot be defined an any rc file. One cannot add this option to the command that launches the client. (There is a "savegame prefix" option one can set from the client, but this string is then further automatically prefixed with the turn number, and setting it to include a path crashes the server.) The current[?] freeciv documentation in the source tarball suggests the "normal" default is the behavior observed with previous versions: "In a local game the games will be saved into the default Freeciv save directory (typically ~/.freeciv/saves/). If you are running the server from the command line, however, any savegames will be stored in the current directory." I suspect this default path is configurable, but I can't find any reference to it in the build configuration files. WORKAROUND: alias freeciv-server="freeciv-server -s ~/.freeciv/saves/" Reproducible: Always Actual Results: Games are automatically saved at root of user's home directory. Expected Results: Games should be automatically saved at "~/.freeciv/saves/"
Correction: *Local* games should be automatically saved at "~/.freeciv/saves/".
Works fine for me. Can you give the command-line that you're using to start the game please? Also, get strace and do strace -o out <whatever you're running here> and attach the out file as text/plain.
Okay, after a bit more checking, it seems that this was only occurring when was earlier forced to start the server from the command line (the closed bug pertaining to IPv6 USE flag), which I was doing without specifying a save directory. When the client launches the server transparently (for a local game), it does indeed specify the ~/.freeciv/saves location). I don't know why it seemed to me this behavior was continuing after we got the transparent launch working, but it's not happening now, so this report is invalid. Sorry for the unnecessary traffic.
