1 synopsis: Configure build-type in terms of Hooks
\r
2 packages: Cabal cabal-install
\r
7 The `build-type: Configure` is now implemented in terms of `build-type: Hooks`
\r
8 rather than in terms of `build-type: Custom`. This moves the `Configure`
\r
9 build-type away from the `Custom` issues. Eventually, `build-type: Hooks` will
\r
10 no longer imply packages are built in legacy-fallback mode. Now, when that
\r
11 happens, `Configure` will also stop implying `legacy-fallback`.
\r
13 The observable aspect of this change is `runConfigureScript` now having a
\r
14 different type, and `autoconfSetupHooks` being exposed `Distribution.Simple`.
\r
15 The former is motivated by internal implementation details, while the latter
\r
16 provides the `SetupHooks` value for the `Configure` build type, which can be
\r
17 consumed by other `Hooks` clients (e.g. eventually HLS).
\r