[Bug 266455] Mk/Uses/go.mk: Update of devel/chroma fails for unclear reason

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266455

Dmitri Goutnik <dmgk@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dmgk@freebsd.org
 Attachment #236634|                            |maintainer-approval?
              Flags|                            |

--- Comment #1 from Dmitri Goutnik <dmgk@freebsd.org> ---
Created attachment 236634
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=236634&action=edit
chroma-2.3.0.diff

It fails because ./cmd/chroma now is in the different module, go detects this
and refuses to build.

Normally, setting GO_MODULE=github.com/alecthomas/chroma/v2/cmd/chroma would
work, but for this port it doesn't because
https://github.com/alecthomas/chroma/issues/528#issuecomment-866370115.

So the hack here would be to stick to modules2tuple, but generate GH_TUPLE
manually using go.mod from ./cmd/chroma, e.g.

$ git clone https://github.com/alecthomas/chroma.git
$ cd chroma/cmd/chroma
$ go mod vendor
$ modules2tuple ./vendor/modules.txt | sed '/chroma/d'

(Ignore generated post-extract caused by nonsensical replace directive in
go.mod.)

Personally, I'd just stop packaging this port until upstream comes to their
senses and makes it go-gettable again.

-- 
You are receiving this mail because:
You are the assignee for the bug.