I don't understand why that flag even exists, if feels like a symptomatic 
misfeature. Just use go install -v, always*

* except when cross compiling. 

> On 16 Jun 2016, at 18:11, Harmen B <har...@typetypetype.net> wrote:
> 
> Or build with `go build -i`
> 
>> On Thu, Jun 16, 2016 at 1:52 AM, Hugh Emberson <hugh.ember...@gmail.com> 
>> wrote:
>> He might be running go test which also seems to rebuild everything every 
>> time unless it has been installed.
>> 
>> go test -i installs all the dependencies for a test and fixes this problem.
>> 
>> 
>>> On Wed, Jun 15, 2016 at 6:14 PM, Dave Cheney <d...@cheney.net> wrote:
>>> My guess is you are using go build, which compiles then discards everything 
>>> it just compiled (unless what was compiled was a main package, in which 
>>> case the binary will be left in your current working directory)
>>> 
>>> I recommend using go install -v rather than go build for general use.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "golang-nuts" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to golang-nuts+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to golang-nuts+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to