Refactor dir structure

[guilhem]

#91 fail because of import like that: github.com/hashicorp/consul/consul/

Contrary to many languages, this type of import ({NAME}/{NAME}) seems to be a bad things in go...
I'm not an expert and don't want to troll, but structure directly by components (like this) seems to be better :/

[mitchellh]

That package is named consul/consul because it happens to be the library portion of consul, rather than the application. The top-level directory is still "main" as you would expect. We do this with all our projects and we haven't had an issue.

Besides "seems to be a bad thing", what is the actual negative affect of a directory named this? If there is a tangible negative effect, then we can discuss, but feelings don't need to come into it.