[pkg-golang-devel] Bug#822746: Bug#822746: golang: Add golang-any dependency package to install either golang-go or gccgo

[Michael Hudson-Doyle]

On 27 April 2016 at 17:57, Anthony Fok <foka at debian.org> wrote:
> On Wed, Apr 27, 2016 at 12:56 PM, Michael Hudson-Doyle
> <michael.hudson at canonical.com> wrote:
>> On 27 April 2016 at 16:27, Anthony Fok <foka at debian.org> wrote:
>>> As per discussion at https://github.com/Debian/dh-make-golang/pull/36
>>> on GitHub, it was decided that a golang-any package should be created
>>> in src:golang instead, so for Go program-type packages that need it,
>>> a simple "Build-Depends: golang-any" suffices in providing the default
>>> Go compiler for each architecture.
>>
>> I've actually done this in Ubuntu as part of the work I did to create
>> separate coinstallable packages for each go major version -- the
>> golang-defaults package:
>>
>>     https://launchpad.net/ubuntu/+source/golang-defaults
>>
>> creates such a golang-any package (the golang-go package this package
>> produces depends on gccgo on !golang arches but that's down to Ubuntu
>> delta that i want to get rid of). I want to do this work in Debian too
>> (in fact there is stuff on alioth that implements this stuff in a
>> (AFAICT) Debian-appropriate way:
>>
>>     https://anonscm.debian.org/cgit/pkg-golang/golang.git/log/?h=debian-sid-coinst
>>     https://anonscm.debian.org/cgit/pkg-golang/golang-defaults.git/
>
> Great work!  This mirrors the existing, time-tested gcc-defaults
> source package,

No kidding :-)

> and I think it is a more comprehensive, flexible and
> future-proof solution and should be the way forward.
>
> This also neatly avoids the kludge that I had to put into debian/rules
> in the patch for src:golang in order to get the package to build
> properly.

Yeah, I like how the golang packaging ends up.

>> I guess I'd like to fix that bug by uploading those changes. I think
>> Tianon was going to try to talk to paultag about this, not sure where
>> that's got to...
>
> Well, the discussion on GitHub happened back in January, and almost
> three months have passed until I finally found time to create a patch
> and filed a Debian bug report.  Obviously, a lot has happened in these
> three months during my hiatus, and I am glad you came up with this
> much-better solution.  :-)

FWIW, I've done a bunch of testing of this, and just posted my results
to bug 818415 which is sort of the master bug for the work I've been
doing. I guess I should add Closes: for this bug to the changelog too.