Add command to automagically create an initial cabal package

[guest]

Don Stewart has a nice tool called mkcabal ( http://www.cse.unsw.edu.au/~dons/code/mkcabal/) which creates an initial cabal package. It would be nice to have this built into the 'cabal' program itself so that "cabal create" or "cabal init" or similar would interactively create a cabal package.

[duncan]

What would be even cooler, once we have the dependency chasing infrastructure is to look for local source files and to generate the exposed module list from that, and the package dependencies and the build-tools etc. All it should need to ask for is the name and initial version number.

The user could then go and remove modules from the exposed list if they thought there were better private.

Indeed it should be possible to tell if it's an executable or a library by checking if there's a Main module.

[duncan]

Just integrating mkcabal should not be too hard. It is apparently now unmaintained as well, so now is a good time to pick it up. Otherwise it's just going to confuse new users who have had it recommended to them.

[byorgey]

Benedikt Huber and I made some good progress on this at the Hackathon today, hopefully a preliminary version will be ready in the next few days!

[duncan]

Sun Oct 11 17:56:44 BST 2009  Brent Yorgey <byorgey@cis.upenn.edu>
  * add 'init' subcommand for initializing project cabalisation

Wed Sep  2 17:03:32 BST 2009  benedikt.huber@gmail.com
  * Collecting some heuristics for creating an initial cabal file

[elga]

*  rio bouygues