That is the bug I'm referring to.
Long term the right solution for me would be to have libraries and executables in different cabal packages, but during initial development it is nice to have everything in the same tree.
The single tree solution helps also with the build of a related website. Although you could split that into its own package as well and inject the results of haddock, coverage, tests etc. from multiple packages into the generated html page, everything is much easier if it is all in one tree. I'll try with having separate packages under a toplevel directory with a Makefile that stitch everything together.