[Canonical-tech] Handling active dependencies in Go

[roger peppe]

On Dec 21, 2012 5:47 PM, "John Arbash Meinel" <john.meinel at canonical.com>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ...
>
> > Say we're using launchpad.net/goose/v1, and we want to change
> > goose in a backwardly incompatible way.
>
> I'm happy to see this tool, and I'll certainly try it out.
>
> I will say that I feel it is fundamentally solving the problem
> backwards. The issue is not so much "we want to change goose in a
> backwardly incompatible way", as "we accidentally changed goose in a
> backwardly incompatible way".
>
> Having a tool that defaults to installing the latest revision of a
> referenced branch means that all dependencies are required to exercise
> extreme caution in what changes they make.  And requires things using
> those to depend on them being very conservative.

Firstly, the tool does not ever install anything. It just changes import
paths and checks for consistency.

Secondly, it has no concept of "latest" - it simply changes things to use
the requested version.

Does that make a difference to your assessment?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20121221/32bf4eaf/attachment.html>