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

Add license metadata #12

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
3 participants
@ambs
Contributor

ambs commented Feb 4, 2017

This is a CPAN Pull Request Challenge pull request.

This time, it defines the two licenses available. Note that although this is not the optimal way, it works: one license directly in EU::MM, the other as "meta_add".

If you do not define LICENSE, and just META_ADD, then you will get three licenses (unknown, artistic and gpl)

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Feb 4, 2017

Coverage Status

Coverage remained the same at 90.152% when pulling 2700600 on ambs:PR/License into caa79d9 on DrHyde:master.

Coverage Status

Coverage remained the same at 90.152% when pulling 2700600 on ambs:PR/License into caa79d9 on DrHyde:master.

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Feb 4, 2017

Coverage Status

Coverage remained the same at 90.152% when pulling 31615f0 on ambs:PR/License into caa79d9 on DrHyde:master.

Coverage Status

Coverage remained the same at 90.152% when pulling 31615f0 on ambs:PR/License into caa79d9 on DrHyde:master.

@DrHyde

This comment has been minimized.

Show comment
Hide comment
@DrHyde

DrHyde Feb 22, 2017

Owner

Thanks, I'll apply this manually seeing that it now conflicts with your other Makefile.PL changes.

Owner

DrHyde commented Feb 22, 2017

Thanks, I'll apply this manually seeing that it now conflicts with your other Makefile.PL changes.

@DrHyde DrHyde closed this Feb 22, 2017

DrHyde added a commit that referenced this pull request Feb 22, 2017

@DrHyde

This comment has been minimized.

Show comment
Hide comment
@DrHyde

DrHyde Feb 22, 2017

Owner

I won't go through all the folderol of a release for all these minor changes, but they'll be in the next release whenever that is.

Owner

DrHyde commented Feb 22, 2017

I won't go through all the folderol of a release for all these minor changes, but they'll be in the next release whenever that is.

@ambs

This comment has been minimized.

Show comment
Hide comment
@ambs

ambs Feb 22, 2017

Contributor

Sure :) 👍

Contributor

ambs commented Feb 22, 2017

Sure :) 👍

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