#100: Remove Setup.hs, use Setup.lhs only
-+--
Reporter: [EMAIL PROTECTED] |Owner: ijones
Type: enhancement | Status: closed
Priority: normal |Milestone:
Component
Ian Lynagh wrote:
On Sat, Nov 25, 2006 at 09:57:50AM -0800, Isaac Jones wrote:
Ross Paterson [EMAIL PROTECTED] writes:
On Wed, Nov 22, 2006 at 01:36:13AM +, Duncan Coutts wrote:
Note that in future we intend to allow there being no Setup.(l)hs at all
when using cabal-setup. No
On Wed, Nov 29, 2006 at 03:32:52AM +, Duncan Coutts wrote:
On Tue, 2006-11-28 at 18:28 +, Ross Paterson wrote:
In that sense, there's only one value (Custom), but defaultMain is
common, and a reasonable number of packages use
main = defaultMainWithHooks defaultUserHooks
Hi
In that sense, there's only one value (Custom), but defaultMain is
common, and a reasonable number of packages use
main = defaultMainWithHooks defaultUserHooks
I had a value for Distribution.Make.defaultMain too (but I don't know
if anyone uses that).
Can't the Simple/Custom
On Mon, 2006-11-27 at 15:06 -0800, Isaac Jones wrote:
Ross, how do you see the fields panning out? Want to implement it? :)
Something like
Build-Type: (Simple|Configure|Make|Custom)
I'd be happy to implement it, if/when we get agreement.
Cool. What do others think of all
Ian Lynagh [EMAIL PROTECTED] writes:
On Sat, Nov 25, 2006 at 09:57:50AM -0800, Isaac Jones wrote:
Ross Paterson [EMAIL PROTECTED] writes:
On Wed, Nov 22, 2006 at 01:36:13AM +, Duncan Coutts wrote:
Note that in future we intend to allow there being no Setup.(l)hs at all
when using
On Sat, Nov 25, 2006 at 09:57:50AM -0800, Isaac Jones wrote:
So a summary of the new rules would be something like:
* Setup.lhs will be found automatically, as it is now.
* Setup.hs will be found and complained about with an error. Maybe in
the interim, we can have a warning. In the
On Sat, Nov 25, 2006 at 09:57:50AM -0800, Isaac Jones wrote:
Ross Paterson [EMAIL PROTECTED] writes:
On Wed, Nov 22, 2006 at 01:36:13AM +, Duncan Coutts wrote:
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
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
