Ticket #518 (closed enhancement: fixed)

Opened 4 years ago

Last modified 17 months ago

reconfigure command that uses the previous configure command

Reported by: guest Owned by:
Priority: normal Milestone:
Component: Cabal library Version: 1.6.0.1
Severity: normal Keywords:
Cc: Difficulty: unknown
GHC Version: Platform:

Description

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.

Change History

Changed 4 years ago by duncan

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.

Changed 3 years ago by duncan

  • status changed from new to closed
  • resolution set to fixed
Wed Aug 25 14:11:06 BST 2010  Dmitry Astapov <dastapov@gmail.com>
  * 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.

Changed 17 months ago by elga

Note: See TracTickets for help on using tickets.