I of course meant 'copies' in that last comment. To clarify what I'm thinking about wrt to juju embedded copies> the source package can ship various embedded code copies but the archive build should use archive golang-*-dev packages whenever possible and where it makes sense (see comment #68 for the list). For example, the archive build of juju should use golang-go.crypto-dev, but juju source package may contain code.google.com/p/go.crypto if code.google.com/p/go.crypto is needed for some other non-archive build.
If both are legitimately needed (and there should be justification for that) to support different clients, then the archive build should use golang-go.crypto-dev from the archive and embed code.google.com/p/go.crypto (justification being, all archive builds should use golang-go.crypto-dev and only juju needs code.google.com/p/go.crypto). I need someone can go through that list in comment 68 and comment on it. Then anything that should be broken out of the juju source (ie, it is not juju-specific) should be into golang-*-dev packages and the archive build should use them and any other existing golang-*-dev packages from the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
