Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update paths for staticcheck and gosimple #11

Closed
sridharv opened this issue Jan 25, 2017 · 0 comments
Closed

Update paths for staticcheck and gosimple #11

sridharv opened this issue Jan 25, 2017 · 0 comments
Assignees

Comments

@sridharv
Copy link
Contributor

The paths have been changed:

From https://groups.google.com/forum/#!topic/golang-nuts/fQQiO4OPdmQ


I have consolidated all of my Go tools in one place at
honnef.co/go/tools (backed by github.com/dominikh/go-tools)

This has changed a number of import paths. The command lines for
the tools now live at honnef.co/go/tools/cmd – for example,
staticcheck has moved from
honnef.co/go/staticcheck/cmd/staticcheck to
honnef.co/go/tools/cmd/staticcheck. Similarly, the supporting
libraries have moved to honnef.co/go/tools as well.

In order to make the transition as pain-free as possible, the old
import paths and GitHub repositories will keep working for a
limited time. Concretely, the following deprecation schedule is in
place:

1. Beginning now, the authoritative place for all code, issues
and pull requests is at github.com/dominikh/go-tools. The old
repositories will not receive new features or bug fixes. The old
import paths will – out of necessity – keep pointing to the old
repositories.

2. Starting March 1st, tools installed from the old locations
will unconditionally exit with a non-zero status code and emit a
deprecation warning. They will otherwise keep functioning like
normal.

3. Starting April 1st, all code in the old locations will be
removed and replaced with a single file causing a build failure,
instructing users to use the new location.

I am sorry for the inconvenience this causes. However, developing
all tools in a single repository will have benefits in the long
run and is worth the disruption.

Cheers,
Dominik
@sridharv sridharv self-assigned this Jan 25, 2017
sridharv added a commit that referenced this issue Jan 31, 2017
sridharv added a commit that referenced this issue Jan 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant