Comment 43 for bug 1267393

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang

On Sat, Mar 29, 2014 at 04:24:22AM -0000, Gustavo Niemeyer wrote:
> [Steve]
> > My biggest concern here is that making golang-go genuinely supportable
> > in the distro context means supporting dynamic linking, and the Go
> > upstream community appears to be quite hostile to the principle of
> > dynamic linking.

> That sounds like an overstatement. It is true that the Go community
> appreciates static linkage, and some members have public sayings about
> how dynamic linkage has its own issues, neither the Go community nor the
> Go core development team (most important in this case) is not hostile to
> dynamic linking.

Ok, thanks for setting me straight on this.

On Mon, Mar 31, 2014 at 01:30:45PM -0000, Mark Ramm wrote:
> I think a key point here is that the juju package does not generally
> install or pull down binaries from anywhere to your machine. It does
> instruct the cloud installation of a server to use a specific ubuntu
> image from simplestreams and a specific jujud binary (also from
> simplestreams) on the remote host.

I agree with Martin; the fact that these binaries do not originate in the
Ubuntu archive, and are not subjected to the normal standards and procedures
for the Ubuntu archive, is very concerning.

Using simplestreams as the distribution method or not makes no difference to
me - but the actual software that's being distributed should be built using
Ubuntu best practices.

We've been turning a blind eye to this so long as the package has been in
universe. I don't think we want juju-core to go into main until jujud is also
brought "in house" in Ubuntu.