-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toplevel alias for "cabal install --install-dependencies" #1484
Comments
I think that a better solution is instead of special-casing Note also that you can save a few keystrokes by using |
I agree completely. That subsumes my solution and need in a pretty flexible way. |
It's my intention for
|
That'd be quite nice, too. Would there still be a "build according to the current packages" command? I'm imagining an edge case where unexpected package upgrades occur due to underspecification.
On Fri, Sep 6, 2013 at 1:27 PM, Johan Tibell [email protected]
|
We're handling that issue differently. There's now an option to put a |
Yeah, it sounds like this feature is already well covered. Glad to hear it and thanks for the great work Cabal maintainers 👍 |
One of the most frequent cabal-install command I use is
cabal install --only-dependencies
. While conceptually it makes sense to have this option under the install mode, it's somewhat inconvenient. I'd like forcabal deps
to be an alias forcabal install --only-dependencies
.Compare, say, Bundler from the Rubygem ecosystem where the default command
bundle
creates and updates a local sandbox directly. It's a compelling workflow:git clone xxx; bundle
.If this were to happen, it would need to accept further command-line flags such as
cabal deps --enable-tests -j2
.The text was updated successfully, but these errors were encountered: