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