You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The path parameter preparation / sanitation at the beginning of the script could do with some refactoring, to:
extract path calculation to functions
store Windows / WSL path sets separately
automatically use the path set which matches the environment of the called executable
In other terms, something like this crude pseudocode:
functionCalculateWinPath {
...
return$WinPathVars
}
functionCalculateWSLPath {
...
return$WSLPathVars
}
# before rdiff-backup execution$Paths[[RdiffBackupExeEnv]::Win] = CalculateWinPath
$Paths[[RdiffBackupExeEnv]::WSL] = CalculateWSLPath
# when referring to paths:$Paths[$RdiffBackupExe.Environment] # for example
Currently it only calculates, stores and uses one type of paths, depending on the environment of the rdiff-backup executable set to be called. This requires both "backup" and "remove" executables to run in the same environment (i.e. Windows or WSL).
This refactoring would allow for removing this current restriction.
The text was updated successfully, but these errors were encountered:
The path parameter preparation / sanitation at the beginning of the script could do with some refactoring, to:
In other terms, something like this crude pseudocode:
Currently it only calculates, stores and uses one type of paths, depending on the environment of the
rdiff-backup
executable set to be called. This requires both "backup" and "remove" executables to run in the same environment (i.e. Windows or WSL).This refactoring would allow for removing this current restriction.
The text was updated successfully, but these errors were encountered: