You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 29, 2018. It is now read-only.
A list of current inaccuracies and inconsistencies I've found in the README's install instructions:
go get -v sourcegraph.com/sourcegraph/srclib-go doesn't work because of the use of Godep and imports that haven't had their import paths rewritten. This should probably be changed to godep get?
Apparently, the src tool was renamed to srclib on srclib's master, but the latest pre-compiled binary is still called src. This duality makes it a bit hard to fix the instructions at the moment
src toolchain add sourcegraph.com/sourcegraph/srclib-go doesn't seem to be a valid command anymore, at least with srclib from current master. Instead, one has to create a symlink manually. Was the removal of that function intentional? Are developers expected to mess around with symlinks?
Should the README on master be correct for the development version of srclib, or for the current release? That is, should references to src be rewritten to srclib already?
A list of current inaccuracies and inconsistencies I've found in the README's install instructions:
go get -v sourcegraph.com/sourcegraph/srclib-godoesn't work because of the use of Godep and imports that haven't had their import paths rewritten. This should probably be changed togodep get?srctool was renamed tosrclibon srclib's master, but the latest pre-compiled binary is still calledsrc. This duality makes it a bit hard to fix the instructions at the momentsrc toolchain add sourcegraph.com/sourcegraph/srclib-godoesn't seem to be a valid command anymore, at least withsrclibfrom current master. Instead, one has to create a symlink manually. Was the removal of that function intentional? Are developers expected to mess around with symlinks?Should the README on master be correct for the development version of srclib, or for the current release? That is, should references to
srcbe rewritten tosrclibalready?