[Hackage] #507: display available flags based on the .cabal file

#507: display available flags based on the .cabal file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Currently cabal configure --help displays only the help for the configure command in general. Often I'd like to say what flags are available for the package in question. Currently the only way to do this seems to be to actually look at the .cabal file in question. Something a bit like: ./configure --help which shows you the generic flags like --prefix but also --enable-glade (for example). -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/507 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects

#507: display available flags based on the .cabal file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: minor | Resolution: Keywords: | Difficulty: normal Ghcversion: | Platform: ---------------------------------+------------------------------------------ Changes (by duncan): * difficulty: unknown => normal Comment: Right. Should not be too hard. After all we do this already in the `cabal info` output. eg: {{{ $ cabal info darcs * darcs (program and library) Synopsis: a distributed, interactive, smart revision control system [..snip..] Source repo: http://darcs.net/ Executables: darcs Flags: curl, curl-pipelining, libwww, http, external-bytestring, external-zlib, haskeline, terminfo, curses, type-witnesses, color, base3 }}} Of course when configuring a single package we want to see the description of each of these flags, if they're available. We could do similarly for `cabal info` when run in the current dir with a local .cabal package. Printing it in `cabal configure --help` is technically a bit harder. Perhaps the help string for `--flags` should refer to `cabal info`. Or perhaps that's just to annoying and we should work out how to get it to read the local `.cabal` file before producing the help output (but not failing if one is not present or if it cannot be parsed). -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/507#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
participants (1)
-
Hackage