[Hackage] #933: cabal configure doesn't suggest cabal install --only-dependencies
#933: cabal configure doesn't suggest cabal install --only-dependencies ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- 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. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/933 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#933: cabal configure doesn't suggest cabal install --only-dependencies ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: Cabal library | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Changes (by kosmikus): * milestone: => cabal-install-0.16 Comment: 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}}}? -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/933#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#933: cabal configure doesn't suggest cabal install --only-dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Changes (by kosmikus): * component: Cabal library => cabal-install tool -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/933#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
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
#933: cabal configure doesn't suggest cabal install --only-dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by tibbe): Replying to [comment:1 kosmikus]: 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. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/933#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
participants (1)
-
Hackage