Support depending on "packages" that contain no Go files

[smarterclayton]

Some Golang projects include directories in their source repository that contain binary content that is necessary for consumers of package code (under version control) but exists in directories that do not contain Go source. It should be possible to declare a Godep dependency on those directories and have them included in order to ensure those dependent directories are included.

Obviously this is a slippery slope, but things like asset folders for vendored JS/HTML/CSS code occur frequently. A workaround is to add a doc.go to make those directories packages, but that isn't always possible with upstream projects.

[freeformz]

What is the use case here? Why would I want to vendor a "package" that I don't use in code?

[smarterclayton]

Because it contains shell scripts or example JSON files that would be used by a test case (so you could run test cases on vendored code), or things like assets (JS, CSS, images) that might be directly referenced by the code.