Re: patch applied (cabal): Use the same ReadP for all compilers, remove CPP hacks

On Tue, 2008-03-11 at 00:39 +, Ross Paterson wrote: > On Mon, Mar 10, 2008 at 05:23:06PM -0700, Duncan Coutts wrote: > > Mon Mar 10 12:14:22 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> > > * Use the same ReadP for all compilers, remove CPP hacks > > If we're bundling a whole copy of ReadP

patch applied (cabal-install): List.hs: fix synopsis paragraph wrapping

Fri Mar 7 11:21:59 PST 2008 Brent Yorgey <[EMAIL PROTECTED]> * List.hs: fix synopsis paragraph wrapping M ./Hackage/List.hs -1 +1 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080307192159-bd4d7-82f35cf1142334c6f7d42b6fea7d25377311.gz

Re: patch applied (cabal): Use the same ReadP for all compilers, remove CPP hacks

On Mon, Mar 10, 2008 at 05:23:06PM -0700, Duncan Coutts wrote: > Mon Mar 10 12:14:22 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> > * Use the same ReadP for all compilers, remove CPP hacks > If we're bundling a whole copy of ReadP then why bother trying to use > the version from the base packa

patch applied (cabal-install): Adapt to using the bundled ReadP

Mon Mar 10 16:36:09 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Adapt to using the bundled ReadP +1 for using the same version of the ReadP lib everywhere, previously we would only have noticed this type error with nhc98. M ./Hackage/ParseUtils.hs -1 +1 View patch online: http://d

patch applied (cabal-install): Make the 'upload' command more self explanatory

Mon Mar 10 16:33:46 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Make the 'upload' command more self explanatory It tells you what to do if you don't supply any args, rather than doing nothing and it check for simple mistakes and gives helpful error messages. M ./Main.hs -1 +20 View pa

patch applied (cabal): Use the same ReadP for all compilers, remove CPP hacks

Mon Mar 10 12:14:22 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Use the same ReadP for all compilers, remove CPP hacks If we're bundling a whole copy of ReadP then why bother trying to use the version from the base package, especially when that requires hacks to use the H98 version with s

patch applied (cabal): Remove the #ifdef'ed unit test code from several modules

Mon Mar 10 12:18:06 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Remove the #ifdef'ed unit test code from several modules They have all been moved to tests/UnitTest/ So we don't need so much CPP in the ordinary modules now. M ./Distribution/PackageDescription/Configuration.hs -78 M

patch applied (cabal): Rearange unit tests some more add extract more tests from the other modules

Mon Mar 10 12:06:51 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Rearange unit tests some more add extract more tests from the other modules ./tests/unitTests -> ./tests/UnitTest ./tests/UnitTest/ModuleTest.hs -> ./tests/UnitTest.hs ./tests/UnitTest/PackageDescriptionTests.hs ->

patch applied (cabal): Reorganise and prune tests/

Mon Mar 10 11:39:38 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Reorganise and prune tests/ Split them into unit tests and system tests. Also remove the rather large bundled HSQL and HUnit packages. We can just depend on HUnit for the tests rather than bundling it. HSQL is very large for

patch applied (cabal): Import Data.Tree rather than defining it locally

Mon Mar 10 09:43:43 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]> * Import Data.Tree rather than defining it locally Since we've dropped ghc-6.2 compatibility we can now use Data.Tree directly. M ./Distribution/ParseUtils.hs -13 +2 View patch online: http://darcs.haskell.org/cabal/_darc

Re: takusen -> cabal -> ArgDescr (2) - my journey + suggestion

> It's used in cabal-install; http://darcs.haskell.org/cabal-install > I can agree the flag business seems confusing at first. so adding simple comments is the best choice then :) Thanks Marc ___ cabal-devel mailing list cabal-devel@haskell.org http:/

Re: takusen -> cabal -> ArgDescr (2) - my journey + suggestion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc Weber wrote: [snip] | What the hell is the third arg in ArgDescr ( OptArg) ? | Where is this used ? ([ a -> [Maybe String]) | argDescrToGetOpt _ ? no, not here | ah in commandShowOptions ? | Wow.. you can print your commandlines again? wow. | But

takusen -> cabal -> ArgDescr (2) - my journey + suggestion

Hi, If you don't have time jump to the last Suggestion section. I'd like to tell you about my reading cabal source journey today.. I wanted to compile takusen using an older Cabal Setup format (without lag) So I wondered who to find a getDefaultVerbosity method.. There is a defaultConfigFlags

Re: [Hackage] #214: Package security

#214: Package security -+-- Reporter: duncan |Owner: Type: task| Status: new Priority: normal |Milestone: Component: misc| Version:

Re: [Hackage] #214: Package security

#214: Package security -+-- Reporter: duncan |Owner: Type: task| Status: new Priority: normal |Milestone: Component: misc| Version:

Re: [Hackage] #89: Sharing of object files between executable builds?

#89: Sharing of object files between executable builds? -+-- Reporter: [EMAIL PROTECTED] |Owner: Type: enhancement | Status: new Priority: low |Milestone: