Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should SPDX.NONE be the default option in 'cabal init --interactive'? #6675

Closed
m-renaud opened this issue Apr 8, 2020 · 3 comments · Fixed by #6677
Closed

Should SPDX.NONE be the default option in 'cabal init --interactive'? #6675

m-renaud opened this issue Apr 8, 2020 · 3 comments · Fixed by #6677

Comments

@m-renaud
Copy link
Collaborator

m-renaud commented Apr 8, 2020

When using cabal init --interactive at HEAD there is no longer a default licence in the prompt list (as of 2fa8302). This means that you can't just press <ENTER> when going through the interactive prompt.

Before (with default, can just press <ENTER>):

Please choose a license:
   1) GPL-2
   ...
 * 7) BSD3
   ...
  14) Other (specify)
Your choice? [default: BSD3] 
Author name? [default: Matt Renaud] 

HEAD:

Please choose a license:
   1) NONE
   ...
  18) Other (specify)
Your choice? 
 is not a valid choice.
Your choice? 1

Should we default this to Flag SPDX.NONE @phadej?

@m-renaud m-renaud changed the title Should NONE be the default option in 'cabal init --interactive'? Should SPDX.NONE be the default option in 'cabal init --interactive'? Apr 8, 2020
@phadej
Copy link
Collaborator

phadej commented Apr 8, 2020 via email

@m-renaud
Copy link
Collaborator Author

m-renaud commented Apr 8, 2020

No worries, if you don't have time to put together a PR I can do that tonight or tomorrow, just lmk!

@phadej
Copy link
Collaborator

phadej commented Apr 8, 2020

Please do. I don't work on Cabal full-time, so any help especially with "trivial" issues is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants