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 reason why scripts are needed to run ci is that a child process normally can not modify a parent process. Specifically, the parent working directory can not be changed from the child process. There may be a way around this for Linux and MacOS. Note the following links that I have not researched yet (recording the issue hastily so I don't forget it):
ci would still require scripts for Windows installations with this enhancement. Build flags would need to be used so that Windows executables still operate by outputting the directory while the Linux and MacOS versions change the working directory.
Note: The idea for this enhancement inspired by this SO answer. Also, this would be a breaking change if implemented after a v1.0.0 release (latest release is v1.0.0-dev.15 as of this writing).
The reason why scripts are needed to run
ciis that a child process normally can not modify a parent process. Specifically, the parent working directory can not be changed from the child process. There may be a way around this for Linux and MacOS. Note the following links that I have not researched yet (recording the issue hastily so I don't forget it):If it is possible to change the parent directory from the child process via plugins with the methods above, then that could enable the following:
go install(orgo get?)ciwould still require scripts for Windows installations with this enhancement. Build flags would need to be used so that Windows executables still operate by outputting the directory while the Linux and MacOS versions change the working directory.Note: The idea for this enhancement inspired by this SO answer. Also, this would be a breaking change if implemented after a v1.0.0 release (latest release is v1.0.0-dev.15 as of this writing).