Having thought about it for a while, I think that this approach is OK, and we can remove the unnecessary Depends: from the -dev binary packages over time. AIUI I'll need a sponsor to upload this change though as it'll go through NEW, anyone keen? :)
On 31 October 2016 at 15:35, Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > I'm attaching a debdiff that implements my idea for this, but it has a > downside: lots of golang-.*-dev packages depend on golang-go (323 in > current sid according to my grep-dctrl). They really shouldn't, but this > hampers swapping out golang-go for gccgo-go in Build-Depends for a test > sbuild. A workaround would be to have gccgo-go Provides: golang-go, which > is awful but does seem to work in my testing and seems nicer than 300-odd > uploads... > > Cheers, > mwh > > On 28 October 2016 at 01:38, Matthias Klose <d...@debian.org> wrote: > >> Package: src:golang-defaults >> >> With the golang-any package it should be possible to use go architectures >> providing only gccgo. As seen in #840190, and I assume in one of the >> golang-defaults bugs, there was the proposal to handle the go and gofmt >> links by >> alternatives. Apparently now silently removed from the golang-defaults >> package. >> With the alternatives approach it was easy to test build a package on >> amd64 >> using gccgo, this is not possible anymore. Please provide an easy way to >> build >> a package using gccgo on architectures which default to golang by default. >> >> _______________________________________________ >> pkg-golang-devel mailing list >> pkg-golang-de...@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel >> > > > _______________________________________________ > pkg-golang-devel mailing list > pkg-golang-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel >