move code into a src directory for easier development/build setup about cli

[bunnymatic]

Sadly, I had all kinds of issues trying to get my machine to build the code and run the tests. I'd love to help try to make that run a bit smoother. And I suspect that moving things into src might help that out, but I don't want to make that mod unless you agree it would be helpful.

[kytrinyx]

Go projects are expected to be like this:

cd $GOPATH/src
tree  -L 3 .
.
└── github.com
    ├── codegangsta
    │   └── cli
    ├── exercism
    │   ├── cli
    │   └── xmetadata
    ├── howeyc
    │   └── fsnotify
    ├── kytrinyx
    │   ├── happimap
    ├── levicook
    │   └── glitch
    └── etc...

This is also where go get puts projects.

It's my understanding that if you want to integrate with other packages, then this is where the code goes -- if you're working on something standalone, then you can put it anywhere.

[bunnymatic]

ok. so when you work on exercism/cli, do you do something like

cd $GOPATH/src/github.com/exercism/cli
glitch

or

  cd $GOPATH/src/
  glitch

and if it's the second, then wouldn't that mean that any go project you work on will have source files sitting around at the $GOPATH/src directory?

[bunnymatic]

I may have figured out the issue. i was checking out the code to /src directly, not to src/exercism/cli/ which meant i had a bunch of garbage at the upper directory.

i get it now. closing this issue.

Once I know things are working, I might update the README a bit.

[kytrinyx]

Yeah, I do this:

cd $GOPATH/src/github.com/exercism/cli
glitch

All of my projects are in the full path (including github.com, where relevant)