What steps will reproduce the problem?

1. Create go source file example/a/a.go with the contents:
  package main

  func main() {}

2. Create go source file example/b/b.go with the contents:
  // +build bug

  package main

  func main() {}


1. go install -tags 'bug' example/a example/b
2. ls $GOPATH/bin/ reports that binaries "a" and "b" exist.

3. Delete both "a" and "b" binaries from bin/ directory; now run:
4. go install -tags 'bug' example/...
5. ls $GOPATH/bin/ reports that only binary "a" exists.

6. Recognize that binary "b" is only generated if specified with an import
path of pkg/b instead of pkg/...


What is the expected output?
The -flags option should handle import paths such as pkg/a pkg/b and pkg/... the same
way (producing two executable's, both "a" and "b", inside bin/
directory)

What do you see instead?
A single executable file, "a", specifically the executable without build tags
is compiled.
The -flags option compiles only the binary "b" if you specify it manually
pkg/b (versus pkg/...)

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g (I think? Ubuntu 12.10, x86, 64 bit, using standard 'go install')

Which operating system are you using?
Ubuntu 12.10 64 bit

Which version are you using?  (run 'go version')
go version devel +21d62bd46e78 Mon Dec 10 01:42:53 2012 -0500 linux/amd64

Please provide any additional information below.

I'm glad to test anything else I can or provide more information if possible / clarify
anything hard to understand, please let me know if there is anything like that.

- Stephen