Logging.path and client repackaging

Hello,

Context:
brand new grr server installed from deb (ubuntu 16.04, grr 3.2.4-6), working perfectly well as is.

Then logs are stored here:
/usr/share/grr-server/lib/python2.7/site-packages/grr_response_core/var/log/

Which is neither standard nor desired. We decided to go for a proper configuration, as per:
https://grr-doc.readthedocs.io/en/latest/maintaining-and-tuning/configuration/contexts.html

By that I mean setting a default "Logging.path":
Logging.path: /var/log/grr/
And specifics ones for non-unix clients.

However, when repackaging clients, the process failed because the logging.path starts with "/":

ERROR:2019-05-08 15:22:19,954 8007 MainProcess 139844161038080 MainThread build:448] Build Config Error: Logging.path starts with /, probably has Unix path. /var/log/grr/

We tried the configuration given as example in the documentation, as well as several other permutation, but it always boils down to one thing: if there is a "default" Logging.path, the repack fails.

The only workaround we found is to specify "/var/log/" for all unix like system, which is subobtimal.

Hence the question, is there any way to configure a "default" logging path and a specific one for windows platform?

Thanks