| In general the users should never have to modify the .cabal file. For
| the common settings that we expect the user to want to control Cabal
| provides configure flags.
|
....
| The idea is that instead of having to find the options for each
| implementation you might want to use, that Cabal knows the right options
| for each compiler to use a feature like optimisation or profiling or
| whatever.
You have a clear mental model of how Cabal is intended to be used -- although
it also provides trapdoors (like ghc-options) for when the intended path isn't
adequate. But that mental model is much clearer to you and the other Cabal
developers than it is to Cabal users like Serge and me.
Would it be worth writing a new section in the Cabal manual that describes the
"intended use model" for Cabal, for the benefit of Cabal users? That way you'd
be able to explain this stuff once and for all.
Documentation often focuses on the knobs ("turn the steering wheel to make the
car change direction"), and omit the larger mental model of what is going on
("cars should be driven on a road").
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
