Re: Enhancement: Default cabal to `-p` profiling enabled

Cabal is not necessarily for developers: For many users it is the way to obtain a recent version of programs like pandoc. Those don't really need profiling libs enabled. If you are a developer, I recommend setting `library-profiling: True` in ~/.cabal/config once and forever, wiping ~/.ghc and reinstalling everything. That said, I agree that the current way to deal with missing profiling/shared/whatever libs is a total pain. A great solution would be if Cabal could simply install development libraries of the existing libraries recursively when a package demands them, just like it installs dependencies recursively in the normal way. On 24/07/14 01:39, Evan Laforge wrote:

On Wed, Jul 23, 2014 at 4:18 PM, Andrew Pennebaker wrote:

...

It can take a while to get a list of this long, full dependency chain. It would be much easier if cabal simply enabled `-p` by default, so we didn't have to think about it.

What do you think?

I'm all for it, I always have to remember to go set profiling true in new cabal installs. If I forget, I just wipe out everything and start again from scratch.

Compile time is 2x, which is crummy, but cabal is for developers, and developers should be profiling, right? _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries