reconfigure command that uses the previous configure command

[bos]

(Imported from Trac #518, reported by guest on 2009-03-05)

Sometimes I make a small change to the .cabal file such as adding an exposed module. Cabal then won't let me build without performing a "cabal configure", however I often have a few flags set, so what I'd like to issue instead is: "cabal reconfigure" which means perform a "cabal configure" with the current set of use flags.
This would be similar to, and a complement to bug 294.

[bos]

(Imported comment by @dcoutts on 2009-03-05)

I think implementing #294 is the better solution. There's no intrinsic need for you to run reconfigure. What you're really trying to do is build.

[bos]

(Imported comment by @dcoutts on 2009-03-05)

Wed Aug 25 14:11:06 BST 2010  Dmitry Astapov <[email protected]>
- Auto-reconfiguration when .cabal is newer than setup-config
  This patch adds "ConfigFlags" to the "LocalBuildInfo" and reuses them to
  perform "configureAction" when .cabal file is changed. This has
  the same effect as re-running "configure" with the most recent used
  set of options, which should be the sensible thing to do.
  Closes #294, #477, #309 and #518.
  

This implements the solution suggested in #294, so we do not need a reconfigure command.