Allow the user to get at the actual default hooks

Duncan Coutts duncan.coutts at
Tue Nov 21 20:37:51 EST 2006

I agree completely. I'd be happy to accept patches along these
lines. :-)


On Tue, 2006-11-21 at 18:47 +0000, Ian Lynagh wrote:
> [forwarding this manually as the BTS doesn't send to a mailing list;
>  the bug is at ]
> Currently, if you want add a hook then there seem to be two starting
> sets of hooks you can use.
> One is emptyHooks, but this really is empty. If you use these hooks then
> setup build will do nothing, for example.
> The other is defaultHooks, but this does more than the defaults; for
> example, it will also run configure.
> The actual defaults should be available as a UserHooks, and a
> UserHooks rather than a Maybe UserHooks should be passed around. At
> first look, the current code is quite hard to follow.
> It would also be nicer if extra hooks could be composed with suitable
> combinators, e.g.
>     theRealDefaultHooks :+: runConfigureHooks :+: someOtherHooks
> and the extra stuff in defaultHooks was broken up into smaller pieces.

More information about the cabal-devel mailing list