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

Closed
bos opened this Issue May 24, 2012 · 4 comments

Projects

None yet

4 participants

@bos
Contributor
bos commented May 24, 2012

(Imported from Trac #933, reported by guest on 2012-03-14)

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.

@bos
Contributor
bos commented May 24, 2012

(Imported comment by @kosmikus on 2012-03-14)

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?

@bos
Contributor
bos commented May 24, 2012

(Imported comment by @tibbe on 2012-03-14)

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.

@nh2
Contributor
nh2 commented Apr 2, 2014

I just hit this - such a warning would be super useful.

@BardurArantsson
Collaborator

This is completely obsolete, given sandboxes. Suggest closing.

@23Skidoo 23Skidoo closed this Jun 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment