When I fork a github repo and use glide create, the package will be my fork repo's link

[Akagi201]

The origin repo is github.com/winlinvip/bms4upyun. When I forked it, it turns to be github.com/Akagi201/bms4upyun

Then when I use glide create in my forked repo. the glide.yaml will be

package: github.com/Akagi201/bms4upyun
import:
- package: github.com/koding/cache
- package: github.com/mediocregopher/radix.v2
  subpackages:
  - pool
  - redis
- package: github.com/ossrs/go-oryx-lib
  subpackages:
  - logger

The package: line should be package: github.com/winlinvip/bms4upyun

[Akagi201]

Will the package: line not use the absolute path name. just use the repo name. In my case, the package: line should be package: bms4upyun

[mattfarina]

Because of the way Go handles paths the fork should be checked out to the same location as the original. Otherwise you will have problems.

If you are specifying a fork as an import set the package to the original name. Then set the repo property to the fork location. Glide will check it out to the original location.