Unexpected behaviour creating a ponzu project

[sirikon]

Using go1.8 there's a 'default' GOPATH, so, it isn't required to install ponzu and use it.

But ponzu requires to have a GOPATH configured, so it can put inside GOPATH/src the new project.

I think that ponzu should do the same, and fallback to the default GOPATH when using Go 1.8.

@nilslice What do you think?

[nilslice]

That is a good point -- I hadn't considered the case when GOPATH env var wasn't available. I suppose the go tool wouldn't export the default $HOME/go to the system if it's not set (if that's even possible).

I think we still need to check for the GOPATH env var, and use it if it exists because many users will have a custom GOPATH defined. In the event that GOPATH env var is not set, we should use $HOME/go or the Windows equivalent (which I believe is available at os/user.User.HomeDir).

This would be a good function to include in the paths.go file..

import "os/user"

func gopath() (string, error) {
    usr, err := user.Current()
    if err != nil {
        return "", err
    }
    gopath := usr.Current().HomeDir

    if (os.Getenv("GOPATH") == "") {
        gopath = os.Getenv("GOPATH")
    }

    return gopath, nil
}

Does that look right to you? If you have time and would like to add this & implement throughout, please go ahead and make another PR. I have a really tight deadline coming up and won't be able to fully change out all the instances of GOPATH checks in the code until after the weekend.

[sirikon]

I would also output on stdout something like "GOPATH env variable is undefined, using default (/home/user/go)"

[nilslice]

Resolved in #87.