New patches in /srv/darcs/git-mirrors/Cabal

commit 7139cf3a07671317feceb5e3b08937ca6ebad87e
Author: Andres Loeh <[email protected]>
Date:   Sat Mar 31 13:42:11 2012 +0000

    choose default solver based on compiler version
    
    GHC-6.12 has base-3 depending on base-4. This is a situation the
    topdown solver is hacked to deal with, but the new modular solver
    currently doesn't support it. We therefore switch back to the
    topdown solver if a GHC version before 7 is detected, but switch
    to the modular solver by default in all other situations.

commit c27994e48c4bf61e62e6843b75c5306626b4b76d
Author: Andres Loeh <[email protected]>
Date:   Thu Mar 15 18:16:26 2012 +0000

    Added a comment

commit 1f9fe7edd57edddfb98adcedc6b209b4b651d1bb
Author: Duncan Coutts <[email protected]>
Date:   Thu Mar 29 02:07:52 2012 +0000

    Use the new --package-db flag stuff in cabal-install

commit c7382db8108f90d7ccf7d507a5b665bab74c3a09
Author: Duncan Coutts <[email protected]>
Date:   Thu Mar 29 02:07:20 2012 +0000

    Extend the --package-db= feature to allow multiple dbs and start from empty
    Previously only one --package-db flag was used (later ones overrode 
earlier).
    Internally we can handle stacks of package dbs, now we expose that fully in
    the user interface.
     --global sets the initial db stack to [GlobalPackageDB]
     --user sets the initial db stack to [GlobalPackageDB, UserPackageDB]
     --package-db=clear clears the db stack to []
     --package-db=global pushes GlobalPackageDB on the top of the stack
     --package-db=user pushes UserPackageDB on the top of the stack
     --package-db=${file} pushes SpecificPackageDB ${file} on the top of the 
stack
    So --global and --user just affect the initial db stack, and this can be
    extended by the --package-db flag, or reset using --package-db=clear.
    
    Note that although this lets users tell cabal to avoid using the global
    package db, we cannot yet stop ghc from looking at the global package db.
    See http://hackage.haskell.org/trac/ghc/ticket/5977
    
    Fixes feature request #437.

commit d812027380ac17a3175a6ba81f602b139f07522f
Author: Duncan Coutts <[email protected]>
Date:   Thu Mar 29 01:46:53 2012 +0000

    head cabal-install requires head Cabal

commit d0f67b4a8797906547dda120027e1bff9ef73af4
Author: Duncan Coutts <[email protected]>
Date:   Thu Mar 29 01:08:37 2012 +0000

    Add back deprecated ghcVerbosityOptions and ghcPackageDbOptions

commit 75b7b8d747cef439cd1dba11db456eef2872ab31
Author: Duncan Coutts <[email protected]>
Date:   Wed Mar 28 22:05:56 2012 +0000

    Fix ticket #731

commit 40acf80fea3c6b3555cfba9fa864006166cd20d4
Author: Duncan Coutts <[email protected]>
Date:   Wed Mar 28 21:45:22 2012 +0000

    Check for the env var GHC_PACKAGE_PATH
    Based on the patch by Keegan McAllister <[email protected]>
    Fixes ticket #335

commit f3bbe9c708ecfd21345f53cda6abac9bb1c059e6
Author: Duncan Coutts <[email protected]>
Date:   Tue Mar 27 23:32:03 2012 +0000

    Break up the component build code a bit
    This will make it easier to allow building individual components

commit 7bb65583935d55acac63ec16bc769abe08b6cd50
Author: Duncan Coutts <[email protected]>
Date:   Tue Mar 27 22:52:05 2012 +0000

    Convert ghc option construction to use an options record
    Using a structured representation of the ghc options rather
    than [String] makes it easier to share and reuse the code
    for building sets of ghc options, which makes it easier to
    add code for calling ghci.
    
    This is based on Sam Anklesaria's GSoC work on "cabal repl"

commit e02a82ff63b84836999e38ef2658cbc47cfc993e
Author: Duncan Coutts <[email protected]>
Date:   Sun Sep 25 05:18:15 2011 +0000

    Add brief description of PVP to cabal init generated .cabal files

commit 97376d4fcc75a2530e0d32402e57ea571560f527
Author: Duncan Coutts <[email protected]>
Date:   Thu Mar 29 01:29:52 2012 +0000

    Bump versions to 1.15 and 0.15
    This is the head branch, the 1.14.x and 0.14.x are in the 1.14 branch.

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to