sm
/
gorigin
1
0
Fork 0
Code Issues Pull Requests Activity
what is the origin of that go binary? http://mcquay.me/gorigin/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
11 Commits
1 Branch
0 Tags
19 KiB
 
Tag: Branch: Tree: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Stephen McQuay b5f5e97438
formatting 		6 years ago
license updated license 8 years ago
main.go report as we find them 6 years ago
readme.md formatting 6 years ago

readme.md

gorigin

Have you ever peered into $GOPATH/bin only to wonder where all that stuff came from?

As someone who originally came from scripting languages where one could trivially peer into an 'executable' using an editor, the origin of binaries in that folder (specifically if GOPATH=~) was completely opaque to me. Not any more!

gorigin helps shed light on this by creating a list of binaries in all the bin folders in the GOPATH and marching through all the src folders in the GOPATH and reporting when a go package with a package name of main matches.