Closed weitzman closed 5 years ago
I'm not fond of giving the process object to addChdir. The transport is given a chance to alter the process object in the configure method. If we called this later, then local transport could cache the cwd when it was provided, and then apply it to the process object in the configure method.
Adjusted as suggested
Tests are passing except for Appveyor which is known failure AFAIK.
Inverted meaning of setWorkingDirectory() as discussed.
I think I'd rather repair setWorkingDirectory calls in the transport rather than swap in SiteProcess, but let's merge like this, as this works, and consider maybe altering later.
Overview
This pull request:
Summary
The current implementation does a setWorkingDirectory() even when the resulting Process is targetting a remote site. Thats not desireable at all, since the directory may be meant for a remote machine.
This PR removes calls to setWorkingDirectory instead relies on the Transport to do this. LocalTransport is the only one to do so.