Skip to content

Set GOPATH and GOROOT for build package to daemon context #327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 14, 2016
Merged

Set GOPATH and GOROOT for build package to daemon context #327

merged 1 commit into from
Feb 14, 2016

Conversation

myitcv
Copy link
Contributor

@myitcv myitcv commented Feb 14, 2016

Ensure the GOPATH and GOROOT are set to the daemon context when building a package.

This handles the situation where the daemon is started under one GOROOT and GOPATH go env, but receives requests in a different go env.

@nsf nsf merged commit 659c0a4 into nsf:master Feb 14, 2016
@myitcv myitcv deleted the fix_build_package branch February 14, 2016 13:57
// TODO: Should read STDERR rather than STDOUT.
out, err := exec.Command("go", "install", p.ImportPath).Output()
out, err := cmd.CombinedOutput()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this change invalidate the comment above? It should either be removed if it's considered done, or changed to:

// TODO: Should read STDERR only rather than STDOUT+STDERR combined.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's okay to remove that comment, output is redirected to log, the more output we have the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants