On 11 July 2017 at 14:43, Michael Hudson-Doyle
<michael.hud...@canonical.com> wrote:
> Maybe it just makes sense for gb to (build-)depend on whichever
> golang-1.X-go directly.

I think you're probably right... :(

(Or perhaps we build-depend on golang-go, and explicitly depend on
whichever package that pulls in?  Although that would make updating it
require a binNMU, which is a bit annoying.)

We can't (easily) just "use whichever version is installed", since gb
has to be recompiled against every Go update.  For that, you might as
well skip the "gb" package and use "go get" instead (as recommended by
upstream).

Additionally, Go itself no longer uses alternatives because then the
software built in the archive might be built against any installed Go,
and package maintainers lose control over which version actually gets
used.

So TL;DR, I think Michael is right -- we probably need to just
explicitly (build-)depend on golang-1.X-go directly, and manually
update the package for each Go release (assuming gb is compatible with
the given release, which this method of updating would also help
ensure).


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to