在使用Golang過程中，我們發現Golang程式缺少依賴庫版本功能是一個非常令人頭大的問題：某些依賴在某個commit之後發生了API變更之後，如果不修改程式碼很難相容，然而開發者之間很有可能因為參與的時間不同，導致執行 go get 命令獲取的版本不同，而導致在不同電腦上出現編譯不通過問題。同時，在多個程式中，如果使用的commit版本不同，也可能會導致程式編譯過程中出現不同的問題。

在Golang1.5之後，Go提供了 GO15VENDOREXPERIMENT 環境變數，用於將go build時的應用路徑搜尋調整成為 當前專案目錄/vendor 目錄方式。Golang在1.5版本引入了實驗性的vendoring標記GO15VENDOREXPERIMENT

go get -u -v github.com/kardianos/govendor

首先有一個名為 test 的專案,

govendor init     #執行一下命令就可以生成vendor資料夾

govendor add +external    #執行命令將當前應用必須的檔案包含進來

下面是govendor詳細命令
[[email protected] fabric-sdk-service-pig]# govendor --help
govendor (v1.0.9): record dependencies and copy into vendor folder
    -govendor-licenses    Show govendor's licenses.
    -version              Show govendor version
    -cpuprofile 'file'    Writes a CPU profile to 'file' for debugging.
    -memprofile 'file'    Writes a heap profile to 'file' for debugging.

Sub-Commands

    init     Create the "vendor" folder and the "vendor.json" file.
    list     List and filter existing dependencies and packages.
    add      Add packages from $GOPATH.
    update   Update packages from $GOPATH.
    remove   Remove packages from the vendor folder.
    status   Lists any packages missing, out-of-date, or modified locally.
    fetch    Add new or update vendor folder packages from remote repository.
    sync     Pull packages into vendor folder from remote repository with revisions
                   from vendor.json file.
    migrate  Move packages from a legacy tool to the vendor folder with metadata.
    get      Like "go get" but copies dependencies into a "vendor" folder.
    license  List discovered licenses for the given status or import paths.
    shell    Run a "shell" to make multiple sub-commands more efficient for large
                 projects.

    go tool commands that are wrapped:
      "+status" package selection may be used with them
    fmt, build, install, clean, test, vet, generate, tool

Status Types

    +local    (l) packages in your project
    +external (e) referenced packages in GOPATH but not in current project
    +vendor   (v) packages in the vendor folder
    +std      (s) packages in the standard library

    +excluded (x) external packages explicitly excluded from vendoring
    +unused   (u) packages in the vendor folder, but unused
    +missing  (m) referenced packages but not found

    +program  (p) package is a main package

    +outside  +external +missing
    +all      +all packages

    Status can be referenced by their initial letters.

Package specifier
    <path>[::<origin>][{/...|/^}][@[<version-spec>]]

Ignoring files with build tags, or excluding packages from being vendored:
    The "vendor.json" file contains a string field named "ignore".
    It may contain a space separated list of build tags to ignore when
    listing and copying files.
    This list may also contain package prefixes (containing a "/", possibly
    as last character) to exclude when copying files in the vendor folder.
    If "foo/" appears in this field, then package "foo" and all its sub-packages
    ("foo/bar", …) will be excluded (but package "bar/foo" will not).
    By default the init command adds the "test" tag to the ignore list.

If using go1.5, ensure GO15VENDOREXPERIMENT=1 is set.