Vgo implements a package manager which is suppose to download dependencies
from some remote host.
It determines where to fetch the code by looking at the import path of the
dependency.
Hence All dependencies which are managed with the new vgo mechanism musst
follow this import path convention.
O
I'm not saying it shouldn't work as you try to do it. I thing vgo is a very
early prototype many corner cases seem to be unsolved. Your problem arises
because the old mechanism (GOPATH) is not there anymore.
I actually think that your replace workaround should work, so maybe you
should file an
Sounds like a job for ffmpeg, there are even Go bindings
https://godoc.org/github.com/giorgisio/goav/avcodec
I have never used it, so no idea if it really fits your bill.
Deployment: It links to a C library, so you may have to deploy those as
well.
Am Donnerstag, 2. August 2018 18:20:24 UTC+2 sc
