Bug 235352 - devel/go-gocode: Please consider deprecating or switching to a supported fork
Summary: devel/go-gocode: Please consider deprecating or switching to a supported fork
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Tobias Kortkamp
URL: https://github.com/nsf/gocode
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-31 12:41 UTC by Dmitri Goutnik
Modified: 2019-04-01 19:48 UTC (History)
1 user (show)

See Also:
tobik: maintainer-feedback-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Goutnik freebsd_committer freebsd_triage 2019-01-31 12:41:47 UTC
devel/go-gocode [1] is no longer maintained and has issues working with Go versions 1.10 and later. Go 1.12 is planned to be released during Feb 2019 meaning that 1.9 (the last version devel/go-gocode is known to work reliably with) will go out of support [2].

Please consider deprecating this port or switching upstream to a supported fork [3].

[1] https://github.com/nsf/gocode
[2] https://golang.org/doc/devel/release.html#policy
[3] https://github.com/mdempsky/gocode
Comment 1 Walter Schwarzenfeld 2019-04-01 19:26:25 UTC
Removed with ports r497504.
Comment 2 commit-hook freebsd_committer freebsd_triage 2019-04-01 19:48:21 UTC
A commit references this bug:

Author: tobik
Date: Mon Apr  1 19:47:24 UTC 2019
New revision: 497510
URL: https://svnweb.freebsd.org/changeset/ports/497510

Log:
  Deprecate devel/go-gocode

  devel/go-gocode has issues working with Go versions 1.10 and later [1].

  [1] https://github.com/nsf/gocode/blob/master/README.md

  PR:		235352
  Submitted by:	Dmitri Goutnik <dg@syrec.org>
  Approved by:	cs (maintainer timeout, 2 months)

Changes:
  head/devel/go-gocode/Makefile
Comment 3 Tobias Kortkamp freebsd_committer freebsd_triage 2019-04-01 19:48:47 UTC
(In reply to w.schwarzenfeld from comment #1)
> Removed with ports r497504.

Not really :p

I'm calling this a maintainer timeout now.  Let's mark this as deprecated.