[Hackage] #947: let "cabal -fSomeFlag" produce error for undeclared flags
Hackage
cvs-ghc at haskell.org
Sat Apr 28 08:33:09 CEST 2012
#947: let "cabal -fSomeFlag" produce error for undeclared flags
---------------------------------+------------------------------------------
Reporter: Oblosys | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: cabal-install-0.14.2
Component: cabal-install tool | Version: 1.14.0
Severity: normal | Keywords:
Difficulty: unknown | Ghcversion:
Platform: |
---------------------------------+------------------------------------------
Changes (by kosmikus):
* version: 1.10.2.0 => 1.14.0
* milestone: => cabal-install-0.14.2
Comment:
There are a few things to keep in mind:
* Flag constraints can be given for arbitrary packages, not just for
targets.
* It multiple targets are specified, -f flags apply to all targets.
* Not every version of a package declares the same flags.
So whatever we end up doing: a warning might be ok, an error almost
certainly isn't. Even a warning has to be designed carefully so that it
isn't just perceived as noise.
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/947#comment:2>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
More information about the cabal-devel
mailing list