Follow recommended project layout about sbctl HOT 5 CLOSED

Nonono. Thank you!

from sbctl.

Looking quickly over the "golang-standards" project it's just subjective stuff. The pkg/ vs internal/ are misnormers as anything inside pkg/ fit for other projects should be separate projects. cmd/main.go is mainly done because there there is just one command, and go install ./... is frankly not how you should install anything , so not sure if I'd like to cater for it....

from sbctl.

Fair enough. I like go install ./... because it allows one to get all the binaries from a repo easily, if there are ever new binaries for this project (doesn't seem likely, though).

Having at least cmd/sbctl/main.go does allow one to build the command without having to specify any output, like so: go build ./cmd/sbctl and go install ./cmd/sbctl. If you feel that isn't useful, I can close the issue.

from sbctl.

Moving to cmd/sbctl/main.go is fine frankly. But I don't feel like sorting stuff into pkg/ nor internal/

from sbctl.

Yeah, fair enough. I will do that, then. Thanks!

from sbctl.