Re: Allow the user to get at the actual default hooks

2006-11-21 Thread Duncan Coutts 
I agree completely. I'd be happy to accept patches along these
lines. :-)

Duncan

On Tue, 2006-11-21 at 18:47 +, Ian Lynagh wrote:
 [forwarding this manually as the BTS doesn't send to a mailing list;
  the bug is at http://hackage.haskell.org/trac/hackage/ticket/101 ]
 
 
 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.


___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel

Re: Remove Setup.hs, use Setup.lhs only

2006-11-21 Thread Duncan Coutts 
On Tue, 2006-11-21 at 18:43 +, Ian Lynagh wrote:

 There are also a couple of larger problems I've had. For example, when
 writing a Makefile that builds all cabal packages in subdirectories
 (i.e. (re)make setup if necessary, configure and build) it is hard (for
 me at least!) to tell make setup depends on whichever of Setup.hs and
 Setup.lhs exists.

Note that in future we intend to allow there being no Setup.(l)hs at all
when using cabal-setup. No Setup.(l)hs file would be equivalent to the
basic one that uses defaultMain.

So how would that affect your makefile?

Duncan

___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel