-
Notifications
You must be signed in to change notification settings - Fork 697
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
cabal init / cabal check inconsistency in allowed licenses #1074
Comments
Thanks for the report. As things currently stand, I'm not sure whether this counts as a bug (or what should be done about it). The specification of the So it is not technically an inconsistency. The question is whether Hackage should allow unrecognized licenses. I will let others weigh in there. |
Ross Paterson told me Hackage was using |
Haha! OK, point taken. =) In any case, it seems to me there are three options:
I have chimed in here since as the maintainer of |
My only concern with (2) is that unrecognized licences is a feature that has been added in the last version of On another note, I do not see (3) as an option. Offering a choice in |
Ah, I see. For reference, it looks like the unrecognized license feature was added by @dcoutts in @d448be2c. |
Hi all! Has any consensus been reached on where to go with this issue? I would like to begin working on this, if a direction has been decided on. |
IIRC @dcoutts still thinks that restricting the set of allowed licenses is a good idea. |
So getting rid of support for Unrecognized Licenses? |
Not in the .cabal parser (because backwards compat), but changing |
@colinwahl Yeah. It's a bit goofy because you just fixed the code to handle unparseable unrecognized licenses better, and now you are going to delete the code, but if you are up for it, go for it! |
This should be obsoleted by the spdx license work, no? |
@phadej, do you agree? |
cabal init
allows me to specify a license that it does not recognize, by using option 11. However,cabal check
, which is used by hackage, rejects an unrecognized field, such as ISC.The text was updated successfully, but these errors were encountered: