[Hackage] #947: let "cabal -fSomeFlag" produce error for undeclared flags
#947: let "cabal -fSomeFlag" produce error for undeclared flags ---------------------------------+------------------------------------------ Reporter: Oblosys | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Typos in flags can lead to confusing problems, especially with large projects that take a long time to build. A simple check could be quite useful: ~> hconfigure -fNonExistentFlag -fSomeFlag cabal: undeclared flag 'NonExistentFlag'. Declared flags are: ExistentFlag, SomeFlag -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/947 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#947: let "cabal -fSomeFlag" produce error for undeclared flags ---------------------------------+------------------------------------------ Reporter: Oblosys | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.10.2.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Description changed by kosmikus: Old description:
Typos in flags can lead to confusing problems, especially with large projects that take a long time to build. A simple check could be quite useful:
~> hconfigure -fNonExistentFlag -fSomeFlag cabal: undeclared flag 'NonExistentFlag'. Declared flags are: ExistentFlag, SomeFlag
New description: Typos in flags can lead to confusing problems, especially with large projects that take a long time to build. A simple check could be quite useful: {{{ ~> hconfigure -fNonExistentFlag -fSomeFlag cabal: undeclared flag 'NonExistentFlag'. Declared flags are: ExistentFlag, SomeFlag }}} -- -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/947#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#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
participants (1)
-
Hackage