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
Some go modules are hosted in subdirs of a git repo; for example, https://github.com/elazarl/goproxy/tree/master/ext has the github.com/elazarl/goproxy/ext module but the repo itself is github.com/elazarl/goproxy. One can use source-subdir to specify the build subdir, but the go-use plugin doesn't respect it.
It's possible, and somewhat common, for a go module to be defined inside a
repo's subdir; in this case we can define source-subdir, but the go-use
plugin needs to use this - otherwise the repo root gets used.
Fixes#978
Bug Description
Some go modules are hosted in subdirs of a git repo; for example, https://github.com/elazarl/goproxy/tree/master/ext has the
github.com/elazarl/goproxy/ext
module but the repo itself is github.com/elazarl/goproxy. One can usesource-subdir
to specify the build subdir, but thego-use
plugin doesn't respect it.To Reproduce
.
part yaml
parts: elazarl/goproxy/ext: override-pull: craftctl default; git checkout a0805db90819 plugin: go-use source: https://github.com/elazarl/goproxy.git source-subdir: ext
Relevant log output
.
The text was updated successfully, but these errors were encountered: