-
Duncan Coutts authored
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.
dfb50c35