[Canonical-tech] Handling active dependencies in Go

Fri Dec 21 17:47:08 UTC 2012

-----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.

We will certainly try to be, but the way the tool is structured means
that mistakes propagate.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDUoJwACgkQJdeBCYSNAAMgjQCcDAfP8hdm/gWBAj44he0/ra9c
+Y4Anj+esILHdr/GPXD0BxI0ycJ1u72/
=oNhj
-----END PGP SIGNATURE-----