You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a case where we need the top-level pkg of a given Go pkg for use in our application and also one of its sub-pkgs b/c it's a CLI. It seemsgpm produces errors in output because it tries to git checkout the sub-pkg even though it's not a submodule but just a sub-directory in the parent pkg.
Fortunately, gpm seems to still work as the binary gets installed in $GOPATH/bin; however, it'd be nice if we could avoid or suppress errors in output from gpm to avoid confusion.
We have a case where we need the top-level pkg of a given Go pkg for use in our application and also one of its sub-pkgs b/c it's a CLI. It seems
gpm
produces errors in output because it tries togit checkout
the sub-pkg even though it's not a submodule but just a sub-directory in the parent pkg.Fortunately,
gpm
seems to still work as the binary gets installed in$GOPATH/bin
; however, it'd be nice if we could avoid or suppress errors in output fromgpm
to avoid confusion.You can see a basic
Godeps
file here along with the errors from runninggpm
: https://gist.github.com/jpfuentes2/ad63ff939a87fdb3d92cAlso, I set
$GOPATH
and$GOBIN
to a temporary directory for the test above and, again, the binary was installed along w/ the pkg.Potential workarounds:
no checkout
whereby the vcs will not attempt to checkout the sub-pkg.Makefile
or other build script usinggo get
after agpm
run.I don't know if any of these ideas are good but maybe something sparks.
The text was updated successfully, but these errors were encountered: