Hi Matthias (belated response sorry)
On 31 March 2015 at 17:33, Matthias Klose <firstname.lastname@example.org> wrote:
> As part of packaging GCC 5, there is now also a gccgo-5 package in vivid. GCC 5
> now builds the go and gofmt commands from it's own source, so the gccgo-go
> package was removed from the distro. gccgo is now based on Go 1.4.2, while
> golang still stays at 1.3. There is a hack in the golang package in that it
> builds empty golang-go and golang-source packages, just to see what can be built
> in the archive, and a lot of things build (including lxd and docker.io), even on
> powerpc after tweaking things.
> A backport for trusty can be found in the ubuntu-toolchain-r/test PPA.
> A co-worker mentioned they would consider filing a FFe for golang, so it may be
> useful to look at the things that will break and need an update, including some
> packages for the phone, so here are some findings (didn't investigate for all of
> these if these are gccgo specific things, or just exposed by Go 1.4).
Do you have a script for doing these kinds of test builds? For other
reasons here at the sprint we were wondering about the feasibility of
backporting go versions to trusty and cobbled together something
involving a ppa with the go 1.4 package from debian experimental,
grep-dctrl, some sed and dput and found that *most* things that
build-dep on golang-go in trusty build with go 1.4:
But well, it was messy. Is there an approved way(tm) of testing this
sort of thing?
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel