Golang relative package import after renaming

Question

My $GOPATH is

\"/Users/peter/goworkspace\"

My current golang version:

go version go1.6 darwin/amd64

I have m

Answer 1

Rule #1: Don't use relative imports. This is (partly) why you're running into issues. Read through this: https://golang.org/doc/code.html#Library

Use the fully qualified import paths (as you showed):

import(
    "project1/package1"  
    "project1/package2"   
    "project1/package3"
    // Or ideally, so others can access it in the future:
    "github.com/<yourusername>/project1/package4"
)  

If for some reason you want to version your package, you can either:

• Provide a new repository (import URL)
• Use a service like gopkg.in (http://labix.org/gopkg.in) to provide versioned import URLs (e.g. gopkg.in/you/pkgname.v2)