title: Internal organizing for golang package with many files
body: <p>I've got a Go library that I'd like to distribute. It's got 62 source files, but I'd like to keep the API in a single package. <strong>Is there a way I can use multiple directories for code in a single package?</strong> It's not a huge amount of source, as the source files themselves are small, and I'd like to keep it that way if possible to make it navigable.</p>
  
  <p>Since it was modeled after similar libraries in other languages, It's currently got two packages: /project and /project/models. After learning more about Go packaging I now realize that this is unwieldy for distribution and use. The user would prefer a single package.</p>
  
  <p>Is there a "gopheric" way of doing this?</p>