The 'executable' flag can get turned off automatically by cabal, e.g. when 
there are mismatched dependencies between the executable and the library.

This is unlikely to be what people want and leads to problems like in 
issue2635.

> The 'executable' flag can get turned off automatically by cabal, e.g. when 
> there are mismatched dependencies between the executable and the library.
> 
> This is unlikely to be what people want and leads to problems like in 
> issue2635.

Do we need this flag at all? With modern cabal we can select which
component(s) to build on the command line, so we would only loose the
ability to configure this statically in cabal.project[.local]. I
personally wouldn't miss that, so if it were just me I would throw it out.

> Do we need this flag at all? With modern cabal we can select which
> component(s) to build on the command line, so we would only loose the
> ability to configure this statically in cabal.project[.local]. I
> personally wouldn't miss that, so if it were just me I would throw it out.

I've had reason to need it in the past, but to be honest I can't
remember why now. I'd like to make a minimal change to 2.14 though,
maybe we can just drop it in 2.15.

The following patch sent by Ganesh Sittampalam <ganesh@earth.li> updated issue issue2636 with
status=resolved;resolvedin=2.15.0 HEAD

* resolve issue2636: make executable flag manual 
Ignore-this: 722c1d3904f01421b669ea46657698e6