Skip to content

Look into Go plugins as a way to run ci without scripts #14

@darylwright

Description

@darylwright

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):

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:

  • installation of a single executable only
  • installation via go install (or go get?)
  • MacOS support, thereby closing Support for MacOS #4

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions