Support --allow-newer in stack init

[mgsloan]

Pretty self explanatory! Would also be good to suggest --allow-newer as something the user can try to possibly make things work.

Should set allow-newer: true in the resulting stack.yaml

[recursion-ninja]

Revisit the semantics of allow-newer be fore perpetuating it's use. See this prematurely closed issue.

[juhp]

I would like to have --allow-newer also for stack install particularly.

[mouse07410]

Somewhat related: how can I specify --allow-newer (or --allow-older) in Stack command line?

Trying to install summoner package, which I don't maintain a local source copy of, building with GHC-9.4.8 (Stack LTS-21.25), but cannot figure how to tell Stack to ignore the bounds - because with existing/defined bounds the installation fails.

I understand something like that can be configured in ~/.stack/global/stack.yaml, but I do not want to enable those globally, or for all/any package built. So, asking for CLI way to do it.

[mpilgrem]

@mouse07410, the short answer is, currently, No. What you are suggesting is the subject of open issue/feature request (as stack install is an synonym for stack build --copy-bins):

• Support --allow-newer for stack build #6501