We currently have a workaround for this in place (run-script.sh defines HOME), but a better fix would to patch the offending GAP library file, i.e. system.g, which accesses GAPInfo.SystemEnvironment.HOME without verifying that it exists. While at that, StringHOMEPath in files.gi also assumes HOME is set without checking, but I think the problematic code path is never triggered.
Of course even better would be to fix this upstream, i.e. in GAP :).
We currently have a workaround for this in place (run-script.sh defines HOME), but a better fix would to patch the offending GAP library file, i.e. system.g, which accesses GAPInfo.SystemEnvironment.HOME without verifying that it exists. While at that,
StringHOMEPathin files.gi also assumes HOME is set without checking, but I think the problematic code path is never triggered.Of course even better would be to fix this upstream, i.e. in GAP :).