Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

reorganize layered tool system (cabal-get, cabal-install, cabal-setup, etc) #72

bos opened this Issue May 24, 2012 · 3 comments


None yet
2 participants

bos commented May 24, 2012

(Imported from Trac #65, reported by @SyntaxPolice on 2006-02-13)

The CabalInstall page describes possible layered tools. Here's the proposal for how it should work.

This is a meta-ticket to track several tasks:

  1. [Thin out cabal-get](#issue/62) so it can be distributed w/ cabal, and have it take over most of the [source:cabal-install/CabalInstall.hs cabal-install] features (trcaking down dependencies locally, not just remotely)
    • sticking point: gnupg. make it optional and highly suggested?
    • Cabal 1.2 should include this thinned out cabal-get
  2. [implement cabal-setup](#issue/63) (or whatever) as a pretty simple layered tool
  3. eliminate the cabal-install layer, [replace with cabal-get](#issue/64).

@ghost ghost assigned SyntaxPolice May 24, 2012


bos commented May 24, 2012

(Imported comment by @dcoutts on 2006-02-13)

As of cabal-1.2 we have a separate cabal-setup that's just a command line wrapper over Setup.(l)hs files and a cabal-install program that downloads and installs packages and deps from hackage.


bos commented May 24, 2012

(Imported comment by @dcoutts on 2007-09-12)

We're planning to merge cabal-setup and cabal-install so that there is one convenient command line UI for developers and users alike (since the two groups overlap).


bos commented May 24, 2012

(Imported comment by @dcoutts on 2007-11-21)

cabal-install has now acquired the features of cabal-setup and cabal-upload.

@bos bos closed this May 24, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment