So I wanted to update a dependency . .

[roger peppe]

On 12 August 2016 at 14:11, Nate Finch <nate.finch at canonical.com> wrote:
> No other repo should ever depend on github.com/juju/juju.

I have to call this out. There is no decent way to use Juju from Go without
depending on github.com/juju/juju.

And backward compatibility isn't insurmountable - dependencies can be locked or
vendored. Juju itself uses many non-backwardly compatible
dependencies, after all.

I think we should be aiming to provide a nice Go API to Juju, whether that ends
up in github.com/juju/juju or not.

  cheers,
    rog.