@Mark: Thanks for these clarifications. So as far as I understand, simplestreams is conceptually way above the juju packaging, as it just selects which built Ubuntu cloud image to fetch and install. So this doesn't seem related to the question of how to build and package juju itself.
These Ubuntu cloud images still need to be built somehow. We usually build all our images (desktop, server, cloud, phone) right our of our Ubuntu archive, so it seems for these this isn't the case as the juju bits of these images are pulled down separately from simplestreams. That's what I (and Adam, Jamie, etc.) object to. It should just use the binary packages instead. However, I realize that this is a much smaller impact than having to download the juju client from simplestreams locally (which is still the case for juju-local though). I have no official saying in that matter as I left the Mir/release teams some time ago, but if we can get away with not having to officially support these golang-go builds and golang-go itself with its current limitations, I'm all for that :-) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
