cabal configure doesn't suggest cabal install --only-dependencies

[guest]

When running 'cabal configure' on a package that has missing dependencies, cabal fails to point out that the dependencies can be installed by running

cabal install --only-dependencies

When cabal is used by millions of programmers, this will cause $1bn in lost productivity.

[kosmikus]

I'm a bit hesitant to add all these warnings and suggestions. For my taste, cabal is often already too noisy.

So let's consider this situation: I think most people come into contact with cabal first via cabal install. Compiling packages locally is mainly interesting for developers. Can't we expect that package developers will already know about cabal install?

As to the --only-dependencies flag. Perhaps I'm missing something, but I think I've never actually used it. Why should it suggest running that and not just suggest running cabal install?

[tibbe]

Replying to kosmikus:

As to the --only-dependencies flag. Perhaps I'm missing something, but I think I've never actually used it. Why should it suggest running that and not just suggest running cabal install?

When developing a library cabal install isn't not what you want, as it would install some intermediate (i.e. unreleased) version of your library in a place where other libraries could start using it by misstake.