On 21 November 2016 at 17:22, Tianon Gravi <tia...@debian.org> wrote:
> On 20 November 2016 at 19:45, Michael Hudson-Doyle
> <michael.hud...@canonical.com> wrote:
> > Check out mwhudson/add-gccgo-go in the golang-defaults repo :)
>
> Nice! My only question after taking a look at the diff is whether our
> "gccgo-go" relation on "golang-any" should be "(>=
> ${source:Version})", same as our "golang-go" relation?
Um, yes, I guess so. Pushed.
>> To be clear, you're talking about adding a new "gccgo-go" virtual
> >> binary package to "src:golang-defaults" which satisfies requests for
> >> "golang-go" via Provides (and thus also provides "/usr/bin/go" via
> >> alternatives or Conflicts)?
> >
> > I took out the Provides: bit for now, it seemed a bit icky, but yes.
>
> Yeah, agreed, especially since switching to "golang-any" is supposed
> to be the official way package maintainers can advertize that they
> support gccgo properly.
>
> I wonder how many packages currently depend on "golang-go" explicitly
> rather than "golang-any".
mwhudson@aeglos:~$ chdist grep-dctrl-sources sid -FBuild-Depends -w
golang-go -sPackage | wc -l
665
mwhudson@aeglos:~$ chdist grep-dctrl-sources sid -FBuild-Depends -w
golang-any -sPackage | wc -l
155
So we're getting there. On the other hand:
mwhudson@aeglos:~$ chdist grep-dctrl-packages sid -FDepends -w golang-any
-sPackage | wc -l
6
mwhudson@aeglos:~$ chdist grep-dctrl-packages sid -FDepends -w golang-go
-sPackage | wc -l
632
Most of those 632 should probably not depend on either really, and some are
of course ok. The number dropped by 20 or so when I updated my sid chdist
so that's good :)
>> Will this simplify the logic behind "golang-any"?
> >
> > Yeah. Actually, more than I had realised! Also pushed to my branch.
>
> Very nice; love how much simpler this is in that regard! Cheers!
>
Yeah, it's nice to get rid of that junk!
Cheers,
mwh
PS: 800 odd golang packages, that seems like a lot?
