search

fpco / stackage-cli

MIT License
28 stars 4 forks source link

Document the splitoff of plugins #50

Open DanBurton opened 9 years ago

DanBurton commented 9 years ago

We moved some plugins, and this caused confusion. Whoops. :( http://www.reddit.com/r/haskell/comments/3526x2/stackage_problems/

For users who wish to install via cabal, the recommended approach should be cabal install stackage.

We should (soon) encourage users to install via stackage-setup; the recommended approach for this should be:

DanBurton commented 9 years ago

I've added libraries with currently-empty modules to the packages that were executable-only. This stops cabal from complaining about executable-only dependencies, and also provides a place to librify some of the functionality in each executable.

The next step is to adjust our advertising from cabal install stackage-cli to cabal install stackage.

DanBurton commented 9 years ago

I added a post-install hook on stackage-cli that is supposed to print a message about how to get some of the plugins. However, for some reason, cabal isn't running this hook. https://github.com/haskell/cabal/issues/2579

snoyberg commented 9 years ago

That bug is... unfortunate.

DanBurton commented 9 years ago

As part of better documenting plugins, we should also have a better error message than "invalid argument" for trying to call something like stackage sandbox when the sandbox plugin is missing. We can have a hard-coded list of known plugins and give more helpful error messages about how to get them.