1.14 doesn't actually build

[Ian Booth]

On 17/09/13 08:59, David Cheney wrote:
>> Is this something godeps handles?  I'd prefer one and only one way to build
>> juju, so we don't have devs doing one thing and the release process doing
>> something else.
> 
> Maybe, it just hasn't been done yet. The release process is it's own
> special monster that existed before godeps arrived at the party.
> 
>> Also, we can't rely on always having the ability to add tags to
>> dependencies. There will likely come a time when we depend on a package we
>> don't control.
> 
> Lets wait til we have that problem before letting it derail our
> current solution. The simple answer is to tag gwacl the way we do
> goose and juju-core, problem solved.
> 

Well, solved for those dependencies. We can't just naively think pulling in tip
from other dependencies (external or otherwise) is a good idea.

The Go ecosystem's lack of proper, mature dependency management tools really
makes me sad. Sigh. Hopefully our tool chain can incorporate godeps or whatever
sooner rather than later.