[Commits] [wesnoth/wesnoth] c87134: wesnothd: Accept 1.12.x by default

[GitHub]

  Branch: refs/heads/1.12
  Home:   https://github.com/wesnoth/wesnoth
  Commit: c87134f36e2af2ef88aa2710cf7c6c1a36bc2058
      https://github.com/wesnoth/wesnoth/commit/c87134f36e2af2ef88aa2710cf7c6c1a36bc2058
  Author: Ignacio R. Morelle <shadowm at wesnoth.org>
  Date:   2014-11-09 (Sun, 09 Nov 2014)

  Changed paths:
    M src/server/server.cpp

  Log Message:
  -----------
  wesnothd: Accept 1.12.x by default


  Commit: 83907ce8caa5b02a58752db4186ec45aba439a6e
      https://github.com/wesnoth/wesnoth/commit/83907ce8caa5b02a58752db4186ec45aba439a6e
  Author: Ignacio R. Morelle <shadowm at wesnoth.org>
  Date:   2014-11-09 (Sun, 09 Nov 2014)

  Changed paths:
    M changelog
    M src/filesystem_boost.cpp

  Log Message:
  -----------
  fs: Fix relative directory creation incongruity with Boost.filesystem

The non-BFS version of create_directory_if_missing_recursive() handles
relative path names (e.g. "foo") correctly and doesn't attempt to create
a parent that is left unspecified in the path (i.e. empty), but the BFS
version does, predictably failing the whole operation.

This fixes an issue where `./wesnoth -p data foo` from the source tree
would fail with `error filesystem: Could not create parents to foo` if
`foo` did not already exist, when using the Boost.filesystem-based
implementation. `./wesnoth -p data ./foo` would succeed because there is
a visible parent directory '.' that already exists and needs not be
created again.


Compare: https://github.com/wesnoth/wesnoth/compare/f5ba94a8a974...83907ce8caa5