On Mon, 10 Jan 2011, Duncan Coutts wrote:
My plan for the command line interface is that cabal configure/build/install in a dir with multiple .cabal files will act on all of them. Individual packages, or components within packages will be selectable by name, e.g. "cabal configure" (configures all packages) "cabal build foo" (builds just target foo).
I'm not quite sure how to handle name clashes, but I expect we can work something out. For example, a package A containing exe A and B. Does A refer to the package (components A and B) or just to the component A?
If you think about all the consequences, then I think the extension to multiple packages in one directory causes more problems than it solves. As I said, my experience so far is, that even multiple packages in one darcs repository do not work well for me. Solution of other problems, e.g. reliable and predictable management of multiple installed versions of a package would be much more important at least for me ...