[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang

[Matthias Klose]

Not addressing the component / archive / PPA questions, but other things
which I think are required.

 - Upstream gc only works on adding shared library support to their C compiler, afaics
   there is currently no work done building shared go libs.

   Adding this seems to be orthogonal, and even if you can't yet do this with gc, then
   you can start developing this with gcc.

   Questions to address are what to put into a shared library.  Just a single Go package,
   or a bunch of packages? E.g. libgo.so as built from gccgo uses this approach. My feeling
   is that with a shared library for each go package we end up with hundreds of new
   libraries.

 - Start thinking how to package and build third libraries built by gc and gccgo. Sure
    Debian already does this, but completely ignores gccgo.

 - Merge our go tool gcc port upstream. Maybe we need a branch for Go 1.2 based
   compilers?

 - Stop bundling every source in juju-core.

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